On Sunday 13 June 2010, C. Meissa wrote:
> Hello list,
>
> A varible ${var1} can be accessed in any subdirectory’s
> CMakeLists.txt.
> However, if those files change ${var1} these changes are not
> accessible from the directory above.
>
> Is there any possibility of getting this done, anyway?
> I n
On Monday 14 June 2010, Tyler Roscoe wrote:
> On Mon, Jun 14, 2010 at 01:40:38PM +0200, Aeschbacher, Fabrice wrote:
> > > > I need to provide easy adding for source files to the developers,
> > > > So it would be nice to just have a CMakelists.txt in every
> > >
> > > subfolder,
> > >
> > > > which
On Mon, Jun 14, 2010 at 01:40:38PM +0200, Aeschbacher, Fabrice wrote:
> > > I need to provide easy adding for source files to the developers,
> > > So it would be nice to just have a CMakelists.txt in every
> > subfolder,
> > > which then edits the source-variable.
> >
> > Also consider to use pr
> > I need to provide easy adding for source files to the developers,
> > So it would be nice to just have a CMakelists.txt in every
> subfolder,
> > which then edits the source-variable.
>
> Also consider to use properties for such a purpose.
Which property do you actually think about?
Regards
Hi again,
Am Sonntag, 13. Juni 2010 schrieb Michael Hertling:
> SET(var1 ${var1} PARENT_SCOPE)
Thank you; that completey solved it!
Thanks again,
C.M.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/o
On 06/13/2010 02:57 AM, C. Meissa wrote:
> Hello list,
>
> A varible ${var1} can be accessed in any subdirectory’s
> CMakeLists.txt.
> However, if those files change ${var1} these changes are not
> accessible from the directory above.
>
> Is there any possibility of getting this done, anyway?
Hello list,
A varible ${var1} can be accessed in any subdirectory’s
CMakeLists.txt.
However, if those files change ${var1} these changes are not
accessible from the directory above.
Is there any possibility of getting this done, anyway?
I need to provide easy adding for source files to the deve
