We've been using CMake for a couple of years for C++ application
building. We effectively set up our CMake project structure once, and
mostly only change it to add new source files, etc.
Currently, all C++ source is checked out of our SVN repository into one
large tree. This tree actually contai
2017-02-09 12:08 GMT+01:00 Martin Craig :
> Hi, got this problem which I've boiled down to a simple test case. My
> source dir contains just one file (realfile) and the installation should
> install this in bin and make a symlink from linkfile to it. This is the
> CMakeLists.txt file:
>
> cmak
Hello Nils,
>> cmake -DX=Y -P x.cmake
>
>
> The above sets the *cache* variable X.
OK, I didn't think that really applied as the script is executed
standalone, so there's no cache in the regular sense of the word.
Thanks for the explanation.
Best regards,
--
DoubleF
--
Powered by www.kitware
On 02/09/2017 04:10 PM, Sergey Zakharchenko wrote:
cmake -DX=Y -P x.cmake
The above sets the *cache* variable X.
This x.cmake gives "X=Y":
SET(X)
MESSAGE("X=${X}")
The above unsets the *regular* variable X (leaving the cache variable X
intact).
This, too, gives "X=Y":
UNSET(X)
MESSAG
Hello list,
I've been using CMake for quite some time and have only now found out
this disturbing difference between SET(X) and SET(X ""). It happens in
cmake -P mode when you try to unset variables which are defined on the
command line, e.g.
cmake -DX=Y -P x.cmake
This x.cmake gives "X=Y":
SET
Dear all,
I recently switched to cmake 3.7.2 on windows 7.
I am building a project with openmp and use find_package(OpenMP).
With cmake 3.5.2 and 3.6.3 the generation of the .sln file for VS 14 2015 works fine.
However, with cmake 3.7.2 I get the error shown below.
All cmake versions were
Hi, got this problem which I've boiled down to a simple test case. My source
dir contains just one file (realfile) and the installation should install this
in bin and make a symlink from linkfile to it. This is the CMakeLists.txt file:
cmake_minimum_required(VERSION 2.8.0)
INSTALL(FILES
