So I want to collect a list of targets which I'll use in a central
CMakeLists.txt. My files are arranged like this:
Project CMakeLists.txt
-Central CMakeLists.txt file which pulls in
o src/CMakeLists.txt
o tst/CMakeLists.txt
-Central CMakeLists.txt file then defines a cu
"DEPENDS all" then
it interprets "all" as a filename and looks for "../all"
I can also use the second form of ADD_CUSTOM_TARGET, but then I need to tie it
to one specific executable, not "all".
Lezz
From: Adolfo RodrÃguez [mailto:dof...@gmail.com]
Sen
ects and assign to ALL_TARGETS, but this is not a good solution
from a maintenance perspective.
Lezz Giles
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages
One question, one suggestion:
If I do specify full paths, doesn't that mean that I'm forcing cmake to use
static linking? Doesn't this preclude one of the advantages of cmake - that
it's easy to switch from static to dynamic linking? (Not that I'm complaining!
I'm definitely going to use Bil
INK_LIBRARIES(hellow fred)
Can anybody help?
Thanks,
Lezz Giles
Soapstone Networks
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake