Actually, the VST host opcodes might well work on Linux with WINE.

The LISP interface will not need any building at all, it will consist of 
CFFI .lisp files. It will almost certainly consist of only 
csound5/interfaces/csound5.lisp.

The Java interface would consist of csnd.jar, period. The source .java files 
are not required.

Java .jar and LISP .lisp files should probably go in the same place as the 
Python interface .so and .py files.

If ATS requires a separate analysis utility, ATS should not be in the Csound 
distribution unless the analysis utility also is included.

How well do the native Csound opcodes work? If they don't work, then I 
strongly recommend Loris as I know that it does work and I build it on Linux 
and Windows.

Loris works very well, with the Python interface you can do analysis as well 
as resynthesis. Loris seems to me to work better -- and more importantly to 
sound better -- than the native Csound opcodes, but I have not put in enough 
time to be fair here. Of course the native Csound opcodes must be included 
for backward compatibility. I am only saying that if they have flaws, a 
better more recent alternative should also be provided.

I have changed my mind about directory structure. You are correct, it should 
be standard for the platform.

Regards,
Mike

----- Original Message ----- 
From: "Istvan Varga" 
To: 
Sent: Saturday, December 03, 2005 5:23 AM
Subject: Re: [Cs-dev] What should be in a release?


> On Thursday 01 December 2005 21:00, Michael Gogins wrote:
>
>> csound binary
>> csound utilities (OK with me if they only run INSIDE csound with -U)
>
> At least on Linux (not sure about the other platforms) it is easy
> to create simple wrappers that emulate the standalone utilities by
> calling csound -U, and this is already done in my package builder
> script. Also, the utilities are quite small when linked dynamically
> against the API library; this may be preferred on Win32.
>
>> FluidSynth opcode
>> Python opcodes
>> VST host opcodes
>> DSSI host opcodes
>> Python interface
>> Jack
>
> I already have these all, with the exception of the VST host opcodes
> that are obviously Win32/Mac only. Of course, on the other hand the
> DSSI opcodes (which are not actually finished, by the way) make sense
> on Linux only.
>
>> LISP interface
>
> What is needed to build that ? What files should be installed, and
> where (see also example file list below for the already existing
> directory structure) ?
>
>> Java interface
>
> Again, what files should be installed, and where ? What dependencies
> are required ?
>
>> Better demos
>
> More specifically ?
>
>> Some sort of pvoc opcode set (Loris/ATS/whatever) as long as it actually
>> works (Note: Loris does work, haven't tried the others).
>
> We already have the pvoc, pvs, and ATS opcodes included by default,
> although for ATS you need a separate analysis utility that is not
> part of Csound.
>
>> Same directory structure on all platforms
>
> While it makes some sense to have a similar structure everywhere,
> it is also important to follow the conventions of the target platform
> so that the package integrates well with the system. There is not
> much benefit from forcing exactly the same structure on all platforms
> at the expense of usability.
>
> ---------------------------------------------------------------------
>
> /usr/lib/python2.4/csnd.py
> /usr/lib/python2.4/csnd.pyc
> /usr/lib/python2.4/csnd.pyo
> /usr/lib/python2.4/lib-dynload/_csnd.so -> ../../../local/lib/lib_csnd.so
> /usr/local/bin/cs
> ...
> /usr/local/bin/srconv64
> /usr/local/include/csound/cfgvar.h
> /usr/local/include/csound/CppSound.hpp
> /usr/local/include/csound/cscore.h
> /usr/local/include/csound/csdl.h
> /usr/local/include/csound/csoundCore.h
> /usr/local/include/csound/CsoundFile.hpp
> /usr/local/include/csound/csound.h
> /usr/local/include/csound/csound.hpp
> /usr/local/include/csound/cwindow.h
> /usr/local/include/csound/filebuilding.h
> /usr/local/include/csound/msg_attr.h
> /usr/local/include/csound/OpcodeBase.hpp
> /usr/local/include/csound/pstream.h
> /usr/local/include/csound/pvfileio.h
> /usr/local/include/csound/soundio.h
> /usr/local/include/csound/sysdep.h
> /usr/local/include/csound/text.h
> /usr/local/include/csound/version.h
> /usr/local/lib/csound/bin/csound
> /usr/local/lib/csound/bin/csound64
> /usr/local/lib/csound/lib/libfltk_forms.so.1.1
> /usr/local/lib/csound/lib/libfltk_gl.so.1.1
> /usr/local/lib/csound/lib/libfltk_images.so.1.1
> /usr/local/lib/csound/lib/libfltk.so.1.1
> /usr/local/lib/csound/lib/liblo.so.0
> /usr/local/lib/csound/lib/libportaudio.so
> /usr/local/lib/csound/lib/libportmidi.so
> /usr/local/lib/csound/lib/libporttime.so
> /usr/local/lib/csound/plugins64/libcontrol.so
> ...
> /usr/local/lib/csound/plugins64/libwidgets.so
> /usr/local/lib/csound/plugins/libcontrol.so
> ...
> /usr/local/lib/csound/plugins/libwidgets.so
> /usr/local/lib/csound/tcl/tclcsound64.so
> /usr/local/lib/csound/tcl/tclcsound.so
> /usr/local/lib/csound/xmg/American.xmg
> /usr/local/lib/csound/xmg/csound.xmg
> /usr/local/lib/csound/xmg/English.xmg
> /usr/local/lib/lib_csnd.so
> /usr/local/lib/libcsound64.a
> /usr/local/lib/libcsound64.so.5.1
> /usr/local/lib/libcsound64.so -> libcsound64.so.5.1
> /usr/local/lib/libcsound.a
> /usr/local/lib/libcsound.so.5.1
> /usr/local/lib/libcsound.so -> libcsound.so.5.1
> /usr/local/lib/pd/extra/csoundapi~.pd_linux
> /usr/local/share/doc/csound/ChangeLog
> /usr/local/share/doc/csound/COPYING
> /usr/local/share/doc/csound/COPYING.FLTK
> /usr/local/share/doc/csound/COPYING.liblo
> /usr/local/share/doc/csound/INSTALL
> /usr/local/share/doc/csound/LICENSE-PortAudio.txt
> /usr/local/share/doc/csound/manual/abetarand.html
> ...
> /usr/local/share/doc/csound/manual/zkwm.html
> /usr/local/share/doc/csound/readme-csound5.txt
>
>
> -------------------------------------------------------
> 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
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 




-------------------------------------------------------
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