On Friday 23 December 2005 16:21, jpff@cs.bath.ac.uk wrote: > >>>>> "Istvan" == Istvan Varga writes: > > Istvan> And now the usual list of problems found: > > Istvan> * the Python interface (csnd.py) is missing, even though _csnd.so is there. > Istvan> Also, the double version does not have _csnd.so and > Istvan> csnd.jar either. > > Where should they go? Did you receive the post quoted at the bottom of this message ? I already answered some of these, but the mail may have been lost. By the way, I have uploaded csound-5.00.0rc1.i686.rpm to the ftp server you mentioned, not sure if you received the message about that (was sent a few hours ago). > Istvan> * the dynamic Csound libraries (libcsound*.so*) are missing > > I can see no sign of these libraries -- basically they are not being built You can build them by adding dynamicCsoundLibrary=1 to the SCons options. It is not a major problem, though, if those files are not included, but having them may be useful. > Istvan> * there are a large number of old binary files included that were built for > Istvan> previous versions of Csound 5 included; these can easily get into the way > Istvan> and cause problems (not to mention the added package bloat): > > Mainly because opcodes were amalgamated without discussion or > agreement. Nevertheless, building from clean sources is a good idea, if the release is built to be actually used. ----------------------------------------------------------------- On Friday 23 December 2005 11:43, you wrote: > I will look into the file oddities in the release. Well, any binary file that is older than your build date is suspicious, but it should always be safe to just build from a clean new checkout. Alternatively, you can try using the cleanup.sh script (run it from the top level csound5 directory where it is); it works well for me, but of course use it with caution like anything that uses the 'rm' command :) > Where should non opcode .so files go? It would be nice to have them installed in a way to integrate well with the external applications like Python (so that one can just "import csnd" in Python without having to fiddle with environment variables), but as a first step it may be enough to just move those files to a separate directory like "interfaces" or similar. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Csound-devel mailing list Csound-devel@lists.sourceforge.net