Hi Toby,

For "scons install", if you use it you need to use the same command
line flags as you use when compiling.  Using scons in this way, the
install targets depend on the build targets, so scons will check if
everything is built, using the commandline parameters given, build
whatever is necessary, then install.  If the flags are different, it
will check if things are built with those flags, so is causing the
rebuild.

"scons install" is something I set up as it works like doing a "make
install" with Makefiles, but Istvan put in an an install.py file to
use which does installation after building and also creates an
uninstall script.  This is more useful now and the documentation
regarding "scons install" should probably be removed at this point
with information explaining how to use install.py put in its place.

steven

On 4/28/06, Tobiah <toby@tobiah.org> wrote:
> I did have portaudio v18.1, and couldn't seem to get anything newer
> from the website, so I build again with usePortAudio=0.  This time
> csound5 built fine, but now I'm having midi probs.
>
> I tried using -M0, and -M1 (The active midi device works, and is /dev/midi01),
> and got the complaint:
>
> error: -+rtmidi='PortMIDI': unknown module
>
> Even though I had not specified portmidi.  I tried building again
> with usePortMIDI=0, but I still got the same complaint.  I tried
> using -+rtmidi='alsa', but I still got the same error.
>
> error: -+rtmidi='alsa': unknown module
>
> I tried just using -M/dev/midi01, but I still get one of the
> above errors depending on whether I include an rtmidi flag.
>
>
>
> Another question regarding scons,
>
> The manual says to run scons with build options, and then run 'scons install'.
> It seems that the second time, scons rebuilds the entire source tree without
> options.  I also didn't know how to clean once I had made changes.  Changing
> from portmidi to not, caused scons to just configure, and then say that everything
> was up to date.  Even when I take a clean source tree, scons builds, but then
> claims that the install target 'csound' is up to date.  I tried puffing the
> installed binary, then scons copies the new one over.
>
> I just don't get how scons works I guess.
>
> Thanks,
>
> Toby
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>