- The Tk is just needed for a csound frontend. It is not needed for the core csound language. Things needed are: libcsound.so, the alsa module, the standard opcode library and a few opcode libraries. - libcsound.so should be everything you need. I will ask about the lib_csnd.so and the printf (haven't seen that one yet).

There are a few things to discuss about init scripts, the csound server etc.
Simon



Dan Williams schrieb:
On Sat, 19 Aug 2006, Simon Schampijer wrote:


Dan,

thanks for your work. Did you took the main csound5 code or is there Barrys and my code included? We were working on a seperate branch and it is possible/likely that the olpc csound code changes form the main csound5 branch. I do not know if Barry has got still in mind to make a fixed point version of csound for olpc. for example.


I used the Csound 5.03.0 sources from sourceforge. I saw there were some config options related to floating point <-> integer conversion, are those anything to worry about? In any case, I haven't done anything specific with your and Barry's code; so if you've got a patch we'll need to bring that in.

A few questions I came up with:

a) What bits require Tk, and was that just a case of somebody writing a tool in the language they knew?
b) What is lib_csnd.so and how does it differ from libcsound.so?  Why two?
c) Why does csound redefine printf()? That leads to compile warnings on pretty much every file.
d) Should there be init scripts to start csound up when the machine starts?

Dan


Simon

Dan Williams schrieb:

I've cleaned up and submitted the csound package to Fedora Extras.  Once
it passes review we should be able to pull it into the image builds
automatically.

If anyone with access to a 64-bit Fedora system could grab the SRPM from
the submission report here and try to build the package, that would be
greatly appreciated.  Doing a 64-bit build of Csound is, um, odd, and
I'd like to verify that stuff ends up in the right place.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203217

Dan


_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel





_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel

Reply via email to