I have some suggestions for consideration:

1. Two installers, one for 32 bit, one for 64 bit samples. This will lend itself to adding a third and even fourth installer for compiling for 64 operating systems without overly complicating the build system. We will expect users who use both versions to install in 2 directories as well.

2. Rework SConstruct to define compiler and linker options for various categories of targets (static libraries, shared libraries FOR csound, the Csound API shared libraries themselves, utilities, console executables, GUI executables). These can be segregated into sections for easier maintenance by those familiar with the respective platforms. 

3. The lists of sources and targets will then be essentially identical on all platforms, except for the options used.

4. Within the Csound directory, build exactly the directory structure that will be installed.

5. Make sure the build system builds the installers and the documentation. There is an SCons add on for the Nullsoft installer, anyway.

Regards,
Mike




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net