I found that having everything in one SConstruct file really made SCons much easier to use. I like things that are easy to use. Just a thought. If you find having SConstript files makes things easy, then that's fine with me.

Best,
Mike

-----Original Message-----
From: Steven Yi 
Sent: Nov 5, 2005 11:55 PM
To: Csound-dev 
Subject: [Cs-dev] CVS Reorganization Request

Hi All,

I've been looking into having separate build directories for the same
src directory and it's a little complicated but makes sense.  One
thing I'd like to do first before all of that is to move all
directories containing sourcefiles  down one level into a src/ folder.
 This would make it *much* easier to use the BuildDir feature in Scons
and allow for easy building of debug and release versions of both 32
and 64 bit csounds.  Their object files would be built in separate
directories so an update file would not require any deleting of
current object files if wanting to switch from 32 to 64.

The drawbacks to moving all directories over to a src/ folder are:

-reorganization of SConstruct file (would maybe start using SConscript
files in addition to SConstruct file)
-loss of CVS history (it'll be there in the old location in the CVS
Attic, but a little trickier to find)

For the first option, I can try the reorganization locally and when I
have it working I can email here to get a firm okay from everyone to
go ahead, and then take care of the changes.  Everyone would have to
do an update after that (with -d) and then proceed from there.

For option B, not much to be done, but could could tag the CVS before
commiting the reorganization, so that the old version can be checked
out and history can be checked against that tagged version for finding
old versions.

For what it's worth, I think it will lead to a more organized project.

I've also looked into the CacheDir feature and it is interesting but a
little wary of using it for fear of things getting out of sync.  It's
sort of a strange feature, but any extra generated files (object
files, binaries, etc.) are stored in a cache, and when you go to
build, if a copy of the generated file doesn't exist, it will check
the cache to see if an already built version that is up to date and in
sync is existent and reuse that if so.  Not sure how useful everyone
would find that feature.

Thanks,
steven


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net