I managed to build csound5 from CVS on my linux box today.
I had to :
upgrade scons to 0.95, 0.94 mangled the compiler flags (it left out the
spaces between the options I think)
I had to upgrade to the latest libsndfile.

So maybe scons could check for the correct versions of these.

When csound5 is to ditributed, the autoconf stuff should be removed or
functional and the README and INSTALL updated (obviously). As a longtime
linux user, I automatically type ./configure && make if I see that stuff
:)

There is also an issue with portaudio.It seems that if you compiled
portaudio with jack support as well as OSS or ALSA you need to compile
portaudio apps with -ljack even if you don't want to use jack for that
particular app.Since the configure output of portaudio says it will
compile in jack even if it won't this took a little while to figure out.

On the scons website there is mention of a standalone scons package tat
can be included in distributed sourcefiles. It would be nice if that is
easy to intergrate, so the users don't have to get additional software to
compile csound.


regards

Gerard

Hi Gerard,

>There is also an issue with portaudio.It seems that if you compiled
>portaudio with jack support as well as OSS or ALSA you need to compile
>portaudio apps with -ljack even if you don't want to use jack for that
>particular app.Since the configure output of portaudio says it will
>compile in jack even if it won't this took a little while to figure out.
>
>  
>

I had added a "useJack" commandline flag to the scons build, so by typing:

scons useJack=1

it will add jack to the LIBS.  I don't know if there's a way to 
programmatically detect if jack was used when compiling portaudio, if 
so, this manual flag should be removed and an automated way to configure 
should be put in.

steven