On 2013-11-10 14:12, Witold E Wolski wrote:
And [_{SOURCE,BINARY}_DIR] are the same as
CMAKE_BINARY_DIR, or CMAKE_SOURCE_DIR.
So why one would use the ${PROJECT}_BINARY_DIR variables?
Not necessarily. Consider:
src/CMakeLists.txt
project(A)
src/b/CMakeLists.txt
project(B)
src/b/tests/CMakeL
On 10.11.2013 17:46, Lars Lars wrote:
Just a follow up question, how does CPack invoke candle and light? On
Windows 7, using Process Monitor I do see these executables being
spawned into a separate process when doing cpack -G "WIX".
I am not entirely sure what you mean by "how".
But you ca
On 10 November 2013 19:12, Witold E Wolski wrote:
> Looking at CMakeLists.txt and trying to anderstand...
>
> the project is:
> PROJECT(LIBFBI)
>
> than there are variables within the the file such as
> LIBFBI_BINARY_DIR
> LIBFBI_SOURCE_DIR
>
> They seem not be set in this script nor in the includ
Looking at CMakeLists.txt and trying to anderstand...
the project is:
PROJECT(LIBFBI)
than there are variables within the the file such as
LIBFBI_BINARY_DIR
LIBFBI_SOURCE_DIR
They seem not be set in this script nor in the included script. Does
cmake generates these variables? If so can anyone po
Thank you for your reply.
Just a follow up question, how does CPack invoke candle and light? On Windows
7, using Process Monitor I do see these executables being spawned into a
separate process when doing cpack -G "WIX".
Lars
Date: Fri, 8 Nov 2013 09:40:37 +0100
From: nilsglad...@gmail.com
To: l
