From: Gerrit V. <vo...@ca...> - 2005-01-22 03:43:18
|
Hi, just short question as sooner or later for the new branch I might have to look into scons. So how close is the current scons structure to what we get with configure ? As I constantly work with 3 or 4 parallel versions of OpenSG the one thing I would really like to have is our classical ./configure <options 1> cd Builds/<config 1> make ./configure <options 2> cd Builds/<config 2> make ./configure <options 3> cd Builds/<config 3> make where (nearly) everything (including the configure call for reuse) is stored inside the Builds/<config X> dir. Another important question is how easy can I manipulate the dependencies, sometimes during development I really want to disable either updating the dependencies or using them at all. Similar how easy can I remove a specific file (like OSGConfigured.h) from being used ? Last one, how easy can I change the compiler options for a single file without that triggering a complete rebuild ?, like switching from -c to -E does not seem to be that straight forward. (Straight forward means just replacing a single character ;-)). Comments welcome as these points are kind of my show stopper for using scons. So before I start digging around (and spending time) if somebody could give me some hints if these things (plus some more, but most of them are similar to the one's above) are doable or not it would help me a bit. thanks & regards, gerrit |