Re: [Rosegarden-devel] scons again

[Chris C. <ca...@al...>]

On Sunday 27 Mar 2005 17:19, Chris Cannam wrote:
>  -- "scons install" only installs the two binaries, nothing else.

Er, and half the time it doesn't even do that:

studio@1[rosegarden]$ rm sequencer/rosegardensequencer
rm: remove regular file `sequencer/rosegardensequencer'? y
studio@1[rosegarden]$ scons
scons: Reading SConscript files ...
Checking for pkg-config ... ok
Checking for alsa >= 1.0 ... ok
Checking for jack >= 0.77 ... ok
Checking for C header file ladspa.h... yes
Checking for lrdf_init() in C library lrdf... no
Checking for liblo >= 0.7 ... failed
Checking for mad >= 0.10 ... ok
Checking for dssi >= 0.4 ... failed
Checking for xft >= 2.1.0 ... ok

scons: warning: Ignoring missing SConscript 'doc/en/SConscript'
File "SConstruct", line 128, in ?

scons: warning: Ignoring missing SConscript 'po/SConscript'
File "SConstruct", line 129, in ?
scons: done reading SConscript files.
scons: Building targets ...
g++ -o sequencer/rosegardensequencer sequencer/mmappedcontrolblock.o 
sequencer/mmappedsegment.o sequencer/rosegardensequencer.o sequencer/main.o 
sequencer/sequencermapper.o sequencer/rosegardensequenceriface_skel.o -Lsound 
-Lbase -L/usr/lib -L/usr/lib -L/usr/X11R6/lib -lasound -lm -ldl -lpthread 
-ljack -lmad -lm -lXft-lfreetype -lz -lXrender -lX11 -lfontconfig -lqt-mt 
-lRosegardenSequencer -lRosegardenSound -lbase -lkdeui -lkdecore
scons: done building targets.
studio@1[rosegarden]$ scons install
scons: Reading SConscript files ...
Checking for pkg-config ... ok
Checking for alsa >= 1.0 ... ok
Checking for jack >= 0.77 ... ok
Checking for C header file ladspa.h... yes
Checking for lrdf_init() in C library lrdf... no
Checking for liblo >= 0.7 ... failed
Checking for mad >= 0.10 ... ok
Checking for dssi >= 0.4 ... failed
Checking for xft >= 2.1.0 ... ok

scons: warning: Ignoring missing SConscript 'doc/en/SConscript'
File "SConstruct", line 128, in ?

scons: warning: Ignoring missing SConscript 'po/SConscript'
File "SConstruct", line 129, in ?
scons: done reading SConscript files.
scons: Building targets ...
scons: `install' is up to date.
scons: done building targets.
studio@1[rosegarden]$ 

"`install' is up to date"?  Huh?  So how do I make it install, then?  Removing 
the installed copy does actually work, but I shouldn't have to do that.

(This definitely isn't just the result of a hash check discovering that the 
installed version is the same, either -- the reason I noticed it hadn't 
installed was that the installed copy is different.  I'm installing to a 
nonstandard prefix, if that makes any difference.)

Speaking of nonstandard prefixes, is there any way to find out what arguments 
I ran "scons configure" with last time around?  I know I can look at 
kde.cachy.py, but the format is quite different -- e.g. if I run "scons 
configure prefix=/blah" the PREFIX variable in that cache file is actually 
unchanged at /usr, but the various KDE variables are redefined -- so I can't 
easily tell from looking at the file what I typed to achieve it.

Finally (for this email), I've changed the sequencer/SConscript to prepend the 
base and sound library directories to the library link path instead of 
appending them.  Otherwise it picks up any dynamic libRosegardenSequencer.so 
that may already be installed in preference to the static 
libRosegardenSequencer.a in the sound build directory.


Chris