Hi Petr,
Thanks for your advices which goes on the line I already explored.
Indeed I have played a bit with similar constructions (either using
functions or macros) and yes it works (simply I thought I had missed
some features in CMake)
One point which forced me to manually add some tricks t
Depends on who knows the directories to be included. If you're in a
situation when B doesn't know which directories A will add, you can
use global properties for this purpose. Something like this:
#-
project(B)
define_property(GLOBAL PROPERTY my_include_files ...)
add_subdirectory(/the
You could create a macro for such purpose:
macro(AddAndInclude directory)
add_subdirectory(${directory})
include_directories(${directory}/include)
endmacro(AddAndInclude)
Usage:
AddAndInclude(/there/A)
Best Regards
NoRulez
Am 19.04.2012 um 16:42 schrieb Christian Arnault :
> Hi,
>
> M
Hi,
My simple work model is as follows:
1) I have two projects A & B, located in independant locations. Both
provide some libraries & executable
2) B makes use of libraries & headers provided in A
I want to launch the build of A together B thus I do:
#-
project(B)
ad