Hi all,

Just gotten back into csound5 and have gotten started with work on the
Scons file.  I've modified it now to add pluginLibrary names to the
pluginLibraries list instead of directly to zipDependencies.  This
pluginLibraries list will be used for building an install target.  

I think I have a pretty good grasp of how to build targets using Aliases
in scons and am planning on working on this the next few days to get the
Scons file a little more organized.  My plans are:

scons install
    - this will install the generated csound binary to /usr/local/bin,
as well as the opcode plugin libraries to /usr/local/share/csound
(please let me know if you think there's a better place for these)

scons release
    - this will create a binary release in a zip file with executables
in csound5/bin directory and opcode plugins in /csound5/lib  (please let
me know if you think there's a better place for these)

scons csound
    - builds csound and utilities

scons csoundVST
    - builds csoundVST

scons installer
    - this will generate installer for the platform being compiled on



This is just a proposal, and it will probably take some time to get
through all of these.  I am planning to add these capabilities as
additional methods of using scons and not replacing or removing any
current features until the new targets are tested to work for everyone. 

Also, in the SConstruct file I checked in, there's a test I did of using
aliases to create a target.  The line:

commonEnvironment.Alias('pdf', commonEnvironment.Command('csound.pdf',
'csound.tex', 'pdflatex $SOURCE'))

allows you to type either of these:

scons csound.pdf
scons pdf

to generate the csound.pdf file.  The long-term plan is to use aliases
to create the targets and to eventually change the default to the
"csound" target (it defaults to build everything currently), so that
targets not called won't generate.  (similar to make files)

Let me know if any of you think there's something I'm missing or
something you'd recommend.

Thanks,
steven