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 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
On 1/8/07, Bill Hoffman <[EMAIL PROTECTED]> wrote:
If you use ADD_SUBDIRECTORY instead of SUBDIRS
it will work as you have it.
-Bill
Ok, thanks for this quick answer, it works like I expected now.
(P.S.: I should have read the man more carefully, since it's written in it.)
__
Julien BIBOLLET wrote:
Hi,
I've simplified a problem I'm encountering:
I have following hierarchie:
|--proj1
|--|--CMakeLists.txt
|--CMakeLists.txt
the proj1/CMakeLists.txt contains:
PROJECT( PROJ1 )
SET( PROJ1_SRCS main.cc )
ADD_LIBRARY( PROJ1 STATIC ${PROJ1_SRCS} )
and the ./CMakeLists.txt co
Hi,
I've simplified a problem I'm encountering:
I have following hierarchie:
|--proj1
|--|--CMakeLists.txt
|--CMakeLists.txt
the proj1/CMakeLists.txt contains:
PROJECT( PROJ1 )
SET( PROJ1_SRCS main.cc )
ADD_LIBRARY( PROJ1 STATIC ${PROJ1_SRCS} )
and the ./CMakeLists.txt contains:
SUBDIRS(proj1)
M
