Hello Zac,
On 09/10/2015 23:27, Zac Bergquist wrote:
> Is there a particular tool or method that one should use to determine
> the appropriate setting for CMAKE_MINIMUM_REQUIRED? By appropriate, I
> mean the earliest version that encompasses all of the features used by
> the project.
This is wha
something like ... ?
file(RELATIVE_PATH variable directory file)
On Fri, Oct 9, 2015 at 2:09 PM, Howard Rubin
wrote:
> Is it possible to get the relative path from PROJECT_BINARY_DIR (or
> CMAKE_BINARY_DIR) to CMAKE_SOURCE_DIR?
>
>
>
> I’m using CMAKE_SOURCE_DIR to add files to *.csproj file (co
Is it possible to get the relative path from PROJECT_BINARY_DIR (or
CMAKE_BINARY_DIR) to CMAKE_SOURCE_DIR?
I'm using CMAKE_SOURCE_DIR to add files to *.csproj file (copied with
configure_file) using CMake on Windows. This results in lots of warnings
like the below that I'd like to get rid of. I
Hello,
Is there a particular tool or method that one should use to determine the
appropriate setting for CMAKE_MINIMUM_REQUIRED? By appropriate, I mean the
earliest version that encompasses all of the features used by the project.
For example, I'm using the CMakePackageConfigHelpers module in a p
Absolutely, as soon as I figure out how to get the overlays working on my
gentoo machine :)
Regards
/R
-- Ursprungligt meddelande--
Från: Raffi Enficiaud
Datum: fre, 9 okt 2015 21:10
Till: cmake@cmake.org;
Ämne:Re: [CMake] CPack Debian
Le 09/10/15 15:37, Robert Bielik a écrit :
> Den 20
Le 09/10/15 15:37, Robert Bielik a écrit :
Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
I saw that Rafael introduced libarchive in commit 7044e8ee4, which
seems to be set to both produce tars without sparse files, and having
root:root as user.
Sorry, that would be Raffi ;)
Yep :)
Targeted
2015-10-09 19:17 GMT+02:00 Domen Vrankar :
> 2015-10-09 15:37 GMT+02:00 Robert Bielik :
>> Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
>>>
>>> I saw that Rafael introduced libarchive in commit 7044e8ee4, which seems
>>> to be set to both produce tars without sparse files, and having root:root as
2015-10-09 15:37 GMT+02:00 Robert Bielik :
> Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
>>
>> I saw that Rafael introduced libarchive in commit 7044e8ee4, which seems
>> to be set to both produce tars without sparse files, and having root:root as
>> user.
>
> Sorry, that would be Raffi ;)
Yes
On Fri, Oct 9, 2015 at 9:53 AM, Laura Médioni wrote:
> Hi,
>
> I am facing a problem with CMake 3.4 under Windows.
> My CMake project is using Qt. Recently I uninstalled Qt and reinstalled it.
> Since then, the previous Qt install keeps on appearing in the
> CMakeCache.txt, leading to link edition
Hello,
Im trying to configure and build a project with the Xcode generator and
the bullseye coverage tool.
Without the bullseye coverage tool it works fine but if I want to use it I
had to do the following workaround:
http://www.bullseye.com/help/tool-xcode.html
In short words, the clan
Hi,
I am facing a problem with CMake 3.4 under Windows.
My CMake project is using Qt. Recently I uninstalled Qt and reinstalled
it. Since then, the previous Qt install keeps on appearing in the
CMakeCache.txt, leading to link edition errors.
Extract of CMakeCache.txt content:
///Dependencies
I saw that Rafael introduced libarchive in commit 7044e8ee4, which seems
to be set to both produce tars without sparse files, and having
root:root as user.
Correct me if I'm wrong :)
Regards
/R
Den 2015-10-09 kl. 14:21, skrev Robert Bielik:
Hi all,
Is there a way to prevent CPack debian bac
Den 2015-10-09 kl. 15:36, skrev Robert Bielik:
I saw that Rafael introduced libarchive in commit 7044e8ee4, which
seems to be set to both produce tars without sparse files, and having
root:root as user.
Sorry, that would be Raffi ;)
Regards
/R
--
Powered by www.kitware.com
Please keep messa
Hi all,
Is there a way to prevent CPack debian backend to tar files as "sparse"
? We have a crossdevelopment project that needs to be unpacked on distro
having BusyBox v.1.20.2,
which does not support sparse files.
Also we need to be able to set owner/group of the extracted files (i.e.
tar s
How can I refer to an environment variable in a generator-agnostic way?
I'm struggling with constructing a functioning install command when
using ExternalProject. I want to allow the following sequence of
commands:
% cmake ..
% make
% make DESTDIR=foo install
The issue I run into i
15 matches
Mail list logo