Hi, On Tue, 2007-02-13 at 09:53 -0600, Allen Bierbaum wrote: > Dirk Reiners wrote: > > Hi Gerrit, > > > > Gerrit Voss wrote: > > > >> Hi, > >> > >> I'm at a stage where I start to change scons and scons-addons frequently > >> so I would like to switch to local copies inside the OpenSG repository. > >> > > > > What do you need to change inside scons? Switching to scons-local is not a > > bad > > idea in general, but changing stuff in there sounds a little troublesome. > > > I agree, this sounds a bit worrisome to me. If OpenSG ends up with > customized versions of SCons and scons-addons, then we will end up with > completely custom build systems that have to be supported.
adding new tool chains (intel compiler, cuda, ...) is just easier inside scons-cons and scons-addons than trying to squeeze them into SConstruct or SConscript. I did not find a way to add new tools to scons-addons (or somewhere else) so that you can use them with a custom tool list when creating the build environment. Similar I did not want to replicate the environment builder or variant-helper from scons-addons which you need to change as you add new tool chains. But maybe I'm just missing something. 'Completely custom' is probably not what we are going to end up with. It's more like the basic versions plus some small tweaks. I don't see a problem in keeping track of the major changes of either scons or scons-addons as vendor branches (that's how I run them locally for now anyway). I don't have a problem with supporting it as I'm going to switch everything we do to scons + scons-addons. That's were some of the changes are initially coming from. But in the end they will be needed for OpenSG. And at the same time they give a 'users perspective' on what I would expect if I start using OpenSG and go on from their to build my own projects. For example some of the stuff in SConstruct (roughly up to line 500) should be in scons-addons (from an OpenSG only perspective). So it is reusable for people who want to write their own applications. Currently you have to copy stuff over to your own project if it contains fcd files or want to use the build info stuff from OpenSG. > Isn't it possible to submit the modifications you need back to the > associated projects? as they are finished and up to the point where they make sense yes. But the time in between (until they are accepted upstream, if they are) is a problem. I don't have a good idea how to do this without having a local copy inside OpenSG. > -Allen Dirk Reiners wrote: > > >> The base build should still work fine with the system wide scons > >> installation just the additional tools would need scons-local. > >> > > > > I'm a little lost here, can you add some details? that was more of a hint that the changes to scons are small enough that the build with standard tool chains still works with whatever scons you use. Only if you would like to use other tool chains you would need to use the modified version. > > > >> The only trick would be some minor changes to the SCONSFLAGS handling > >> which currently does not work well. (Typicall windows path with spaces, > >> whitespaces in general) > >> > > > > I haven't used that, options.cache.* has been working fine for me so far. > > WHat > > do you use it for? The problem is OpenSG is only one of the things using scons (that's where that problem originally came from). So I guess I could find a way not to push that to scons-local inside OpenSG ;-) as it really is not coming from there. I just ran a diff and had a look what I already changed ;-) > > > >> I also would like to remove the ******** cvs_ids. They are a pain during > >> merging as they change to often. And with subversion there is no real > >> need to keep them as a single revision identifies all files. > >> > > > > No objection at all, I've just been reluctant to touch absolutely > > everything. ok, I slowly will start to remove them. regards, gerrit ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
