[CMake] Re: Avoiding convenience libs

Kishore, Jonnalagadda (IE10) Kishore.Jonnalagadda at honeywell.com
Thu Apr 19 01:12:46 EDT 2007


> -----Original Message-----
> From: cmake-bounces+kishore.jonnalagadda=honeywell.com at cmake.org
> [mailto:cmake-bounces+kishore.jonnalagadda=honeywell.com at cmake.org] On
> Behalf Of Pascal Fleury
> Sent: Wednesday, April 18, 2007 3:45 AM
> To: cmake at cmake.org
> Subject: Re: [CMake] Re: Avoiding convenience libs
> 
> On Tuesday 17 April 2007 23:55:44 Matthew Woehlke wrote:
> > WAG: variables only propogate to children, not siblings (i.e. 'not
to
> > later CMakeLists.txt's that are not children)? IOW, try moving your
> > SET() up to a common parent.
> 
> Well, zes, that is what I noticed. But as other things in cmake are
> clearly "script-like" with a well-defined control flow (including
dirs,
> if/else, loops, etc), it seems bizarre that the scoping of such
variables
> is
> depending on the file hierarchy not the call-tree. Is there a way to
have
> this vars be visible between siblings ?

Place the variables in CACHE. You could try:

SET(utils_SRCS a.cpp b.cpp CACHE INTERNAL "" FORCE)

Warm regards,
Kishore


More information about the CMake mailing list