23 Apr
2004
23 Apr
'04
11:15 a.m.
Greetings:
I'm happy to see and hear another release of CheeseTracker, but I have
a couple questions regarding SCons. I'm not opposed to its use, it
appears to resolve many issues for cross-platform builders, but since it
is relatively new (and I'm relatively old) I'm a little confused by it.
The SCons FAQ is pretty much just useless history and doesn't answer the
following questions:
1. Apparently SCons does without the need for anything like 'make
depend' or 'make clean'. If that's true, does it mean that SCons builds
fresh every time, i.e., that it autoerases the compiled objects ?
2. If something like 'make clean' is supported, how do I invoke it ?
What can I do if I don't want automatic erasure of the object files ?
3. No man pages, that sucks on a UNIX/Linux platform. The GNU
autotools have them, SCons should have them too.
4. No 'scons uninstall' ?? Again, if I'm missing it, please inform
me how it's invoked.
CT and Csound are now the only two apps on my system that use SCons.
The maintainers of Csound couldn't make the autotools work for
themselves, so now you must add downloading and installing SCons (and an
up-to-date Python) to the process of building Csound. Happily, that
isn't especially difficult, but it does add another layer of complexity
to the process. More to the point, why don't the mainstrean Linux
distros include SCons as a matter of course ?
Best,
dp
23 Apr
23 Apr
2:43 p.m.
On Friday 23 April 2004 10:45, Dave Phillips wrote:
Greetings:
I'm happy to see and hear another release of CheeseTracker, but I have
a couple questions regarding SCons. I'm not opposed to its use, it
appears to resolve many issues for cross-platform builders, but since it
is relatively new (and I'm relatively old) I'm a little confused by it.
The SCons FAQ is pretty much just useless history and doesn't answer the
following questions:
1. Apparently SCons does without the need for anything like 'make
depend' or 'make clean'. If that's true, does it mean that SCons builds
fresh every time, i.e., that it autoerases the compiled objects ?
It's indeed fresh every time, it doesnt really precompute anything before
building.. though detection for now is up to the user.. which is still
not much problem since nowadays we have pkg-config..
2. If something like 'make clean' is
supported, how do I invoke it ?
What can I do if I don't want automatic erasure of the object files ?
scons -c
is just like make clean
3. No man pages, that sucks on a UNIX/Linux platform. The GNU
autotools have them, SCons should have them too.
"man scons" works for me..
4. No 'scons uninstall' ?? Again, if I'm missing it, please inform
me how it's invoked.
Oh I forgot the target.. I think that's up to the user to do for now..
CT and Csound are now the only two apps on my system that use SCons.
The maintainers of Csound couldn't make the autotools work for
themselves, so now you must add downloading and installing SCons (and an
up-to-date Python) to the process of building Csound. Happily, that
isn't especially difficult, but it does add another layer of complexity
to the process. More to the point, why don't the mainstrean Linux
distros include SCons as a matter of course ?
Debian does... and I believe gento too..
though not sure about redhat-based distros..
Cheers!
Juan Linietsky
3:04 p.m.
CT and
Csound are now the only two apps on my system that use SCons.
The maintainers of Csound couldn't make the autotools work for
themselves, so now you must add downloading and installing SCons (and an
up-to-date Python) to the process of building Csound. Happily, that
isn't especially difficult, but it does add another layer of complexity
to the process. More to the point, why don't the mainstrean Linux
distros include SCons as a matter of course ?
Debian does... and I believe gento too..
though not sure about redhat-based distros.. 
7:07 p.m.
el Fri, 23 Apr 2004 09:45:52 -0400
Dave Phillips <dlphilp(a)bright.net> escribió:
I'm happy to see and hear another release of
CheeseTracker, but I have
a couple questions regarding SCons. I'm not opposed to its use, it
appears to resolve many issues for cross-platform builders, but since it
is relatively new (and I'm relatively old) I'm a little confused by it.
heh heh, similar feeling here...
CT and Csound are now the only two apps on my system
that use SCons.
The maintainers of Csound couldn't make the autotools work for
themselves, so now you must add downloading and installing SCons (and an
up-to-date Python) to the process of building Csound. Happily, that
isn't especially difficult, but it does add another layer of complexity
to the process.
scons was not too problematic to build and install, although a little
confusing at first. but now that it's installed, i've had no luck with
csound5, compilation fails somewhere on the way. what about you, have you
had better luck? or anyone?
BTW, my installation has no man page either.
--
24 Apr
24 Apr
1:15 p.m.
luis jure wrote:
scons was not too problematic to build and install,
although a little
confusing at first. but now that it's installed, i've had no luck with
csound5, compilation fails somewhere on the way. what about you, have you
had better luck? or anyone?
BTW, my installation has no man page either.
I just built and ran Csound5, using today's (April 24) CVS sources. The
compile stalled until I realized I needed to add useJack=1 to the scons
command. So far I've tested the trapped.csd in the examples directory
and a test file for MIDI input. The CSD file played very well in
realtime, but the MIDI input was absolutely awful, with the worst
latency I've heard from Csound in years. IIRC, none of the Csound5
development group has a working Linux MIDI system, so I don't have high
hopes that it's going to be corrected soon. Also, it should be noted
that Csound5 is only in beta right now, so it would be unfair to judge
it while still incomplete. I haven't yet tried it with Oeyvind
Brandtsegg;s ImproSculpt, but again I don't have high hopes, too many
needed opcodes were missing from Csound5 the last time I tried it with
Oeyvind's file.
It's a great shame that Istvan Varga's contributions from years ago
haven't been worked into canonical Csound yet. I'm seriously considering
returning to his sources and trying again to build them under RH 9. I
ran into some deep problems the last time I tried to compile it here,
perhaps I'll dig into the sources this time and find how to fix it.
Btw, I installed SCons myself some time ago, when Planet C wasn't
up-to-date with CheeseTracker, so I don't have the default Planet C
installation. I even updated to the latest version, but I still don't
have a man page for SCons...
Best,
dp
8:45 p.m.
>scons was not too problematic to build and
install, although a little
>confusing at first. but now that it's installed, i've had no luck with
>csound5, compilation fails somewhere on the way. what about you, have you
>had better luck? or anyone?
>
>BTW, my installation has no man page either.
>
[MUNCH]
Btw, I installed SCons myself some time ago, when
Planet C wasn't
up-to-date with CheeseTracker, so I don't have the default Planet C
installation. I even updated to the latest version, but I still don't
have a man page for SCons...
For some reason the install target for scons does not install the man
pages. I had to "manually" install them for my packages. Look in the
source directory, they are there. Gzip them and copy to (this is what is
part of my package):
# rpm -q -l scons|grep man1
/usr/share/man/man1/scons.1.gz
/usr/share/man/man1/sconsign.1.gz
-- Fernando
7592
days inactive
7593
days old
linux-audio-user@lists.linuxaudio.org
5 comments
4 participants
participants (4)
-
Dave Phillips -
Fernando Pablo Lopez-Lezcano -
Juan Linietsky -
luis jure