Hi, On Tue, 2008-11-04 at 10:09 -0300, Thiago Bastos wrote:
> > > With CMake you usually glob all header files and include them in the > build (so they are also included in VS/Xcode projects). It works fast > and very well for us. SCons dependency scanners are nice, but quite > honestly, I was glad to sacrify them in favour of much faster builds > (and no problems so far). > > PS: remember that packaging and installation is MUCH MUCH better in > CMake ;-) > I'm partially looking into this after trying to figure out why scons doesn't want to build native win64 stuff. And OS X seems to be broken too, looking at more recent mails. So one general question for the cmake users, how do I propagate information, e.g. lists of values, up. E.g. from a subdir cmakelists.txt to the ones above. Ideally without writing it to files. But looking at OpenSG's structure it might be the best to traverse the source tree and write out files and use these to setup all the targets as a second step. As a concrete example, how do I tell the OSGSystem build env. where to find the OSGBase includes. Ideally I want to get away from the scons way of either finding it locally via include"" or in the global install dir. That just does not seem to work well and is the worst part of the scons build system. Switching to include <> might be a solution, but I'm not sure how to handle the OpenSG subdir part of #include<OpenSG/XX> thanks & kind regards, gerrit ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
