Hi John,

> > I think the fluid opcodes should be in as well, as we discussed this
> > weekend it gives users access to a lot of sample playing possibilities
> > right out of the box.
>
> I am building libfluidOpcodes.so in my 4 packages

Great!

> > What about some of the other opcode sets:
> >
> > -FLTK
>         ?? Do you mean widgets?  If so in

Yes, I was referring to the widgets.  Glad that is in as well.

> > -STK
>         Do not have these

I don't know if these are documented in the manual either.  This has
opcode library has a source dependency that requires STK sources to be
copied into the Opcodes/stk folder.  Is this folder missing for you? 
I think it requires buildStkOpcodes=1 as well.

> > -Loris
>         In
> > -OSC
>         In
> > -python
>         In
> > -ladspa/dsssi (Linux only)
>         I think these are in, but not sure if they are finished

Last I remember, LADSPA was working but dsssi still had issues. 
They're documented in the manual and seem to be working as well as
they have been.

> >
> > and also csound~ for PD?
>
>         Do not know how to build

I actually never built until just now; requires setting buildPDClass=1
and having pd development headers (m_pd.h is listed in scons -h).

BTW: regardless of include base dir (i.e. /usr/include,
/usr/local/include), are the headers going into "Csound" or "csound"
or neither?  I seem to have both here from running installs so can't
remember who's releases did what, but this affects end users who will
develop on top of the C API if it is not consistent.  My preference is
for "csound", i.e. "/usr/local/include/csound" with all relevant
headers there.  Any thoughts?

steven

steven


-------------------------------------------------------
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_idv37&alloc_id865&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net