> Specifying a user binary specfile for CPack RPM packages is done like this:
>
> set(CPACK_RPM_blah_USER_BINARY_SPECFILE blah.spec.in)
>
> The documentation says the "specified file will be processed by
> configure_file( @ONLY)." However, exactly which variables are available for
> substitution? I
Specifying a user binary specfile for CPack RPM packages is done like this:
set(CPACK_RPM_blah_USER_BINARY_SPECFILE blah.spec.in)
The documentation says the "specified file will be processed by
configure_file( @ONLY)." However, exactly which variables are available for
substitution? Is there a li
On 08/02/16 19:35, Alain Miniussi wrote:
> On 08/02/2016 18:43, Alain Miniussi wrote:
>>
>> Hi,
>>
>> I am trying to fix FindHDF5.cmake (support for HDF5_ROOT is broken,
>> only environment variable is supported and it will be eventually
>> probably ignored in find_program).
>>
>> To that end, I'd
On 08/02/2016 18:43, Alain Miniussi wrote:
Hi,
I am trying to fix FindHDF5.cmake (support for HDF5_ROOT is broken, only
environment variable is supported and it will be eventually probably ignored in
find_program).
To that end, I'd like to copy it in my source tree and use that version inste
Hi,
I am trying to fix FindHDF5.cmake (support for HDF5_ROOT is broken, only
environment variable is supported and it will be eventually probably ignored in
find_program).
To that end, I'd like to copy it in my source tree and use that version instead
of the one in /usr/shared/cmake.
Accord
On Mon, 8 Feb 2016 10:31:17 -0500, Brad King said:
>Sean, it looks like you are still running nightly tests on OS X
>10.6 with Xcode 4.2:
>
> https://open.cdash.org/viewNotes.php?buildid=4226138
>
>and OS X 10.5 with Xcode 3.1:
>
> https://open.cdash.org/viewNotes.php?buildid=4226202
Yeah, most
On 02/07/2016 01:54 PM, Michael Jackson wrote:
>> What is the oldest version of OS X that CMake actually runs on?
>> I guess I would support the last version of Xcode that actually
>> ran on that platform. In reality this is probably 10.6.8?
[snip]
On 02/08/2016 10:21 AM, Sean McBride wrote:
> What
On 02/07/2016 01:54 PM, Michael Jackson wrote:
>> What is the oldest version of OS X that CMake actually runs on?
>> I guess I would support the last version of Xcode that actually
>> ran on that platform. In reality this is probably 10.6.8?
[snip]
On 02/08/2016 10:21 AM, Sean McBride wrote:
> What
On Sat, 6 Feb 2016 11:49:07 +0100, Gregor Jasny via cmake-developers said:
>I'd like to get your feedback on deprecating or dropping support for
>older Xcode versions. During changes on the Xcode generator it gets
>harder and harder to test against old and very old Xcode versions like 3
>and 4.
>
Scott,
Rather than having the versions fight one another in BOOST_ROOT, you might
consider modifying the CMAKE_PREFIX_PATH to include the versions of boost you
have - find_package will search there first (you might be able with just giving
it the parent of the boost version). If you set the ve
On Mon, Feb 8, 2016 at 1:56 PM, Victor Leschuk wrote:
> Hello, I am trying to use clang with cmake on Windows.
>
> I have compiled LLVM+clang using Visual Studio 2015. And now I am facing
> problems with building cmake projects using this clang. It looks like cmake
> is trying to pass wrong optio
Hello, I am trying to use clang with cmake on Windows.
I have compiled LLVM+clang using Visual Studio 2015. And now I am facing
problems with building cmake projects using this clang. It looks like
cmake is trying to pass wrong options to linker.
Here simple test project:
$ cat CMakeLists.tx
hello cmake community, just re-pasting what I've already posted on Qt
forums:
I'am experiencing some abysmal compilation time when it comes to building a
relatively small Qt5 app in windows.
The problem resembles alot the reported here issue :
http://lists.qt-project.org/pipermail/interest/2015
Hi Lars.
No, that's a "bug" in your command-line. In cmd, the caret ^ is used as a
general escape character for escaping spaces, pipes etc. But to escape
quotes, a backslash \ is used (yes, the escaping rules in cmd are weird).
So the backslash preceding the quote is taken by cmd to be an escape
c
Hello,
Using Windows 7 SP1 and cmake 3.3.0
The first command below works (starts calc) when execute in cmd shell. The
second command produces the error message "cmake -E env: no command given". Is
this a bug in cmake?
"C:\Program Files (x86)\CMake\bin\cmake.exe" -E env "PATH=C:\temp" calc
"
Hi Scott.
Regarding the delimiters: you'd see them if you included the dereference in
the quotes: "Boost root: ${BOOST_ROOT}". When outside quotes, the
delimiters are effectively swallowed up by message().
Regarding the main issue: I could be wrong, but from a quick glance at the
FindBoost.cmake
16 matches
Mail list logo