[PD-dev] including [dssi~] in Pd-extended

[Frank Barknecht]

Hallo,
Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:

> CVS is a tool for managing source code,  
> which is what we would need to do in order to include fluidsynth and  
> DSSI plugins.  We don't need to make changes to the fluidsynth  
> source, that would indeed complicate things.  We would only import  
> stable versions known to work well with Pd.
> 
> This is already happening in many places and I think it make good  
> sense here.  For example:
> 
> externals/grill
> GemLibs
> externals/hcs/hid/linux/input.h
> externals/hcs/hid/HID Utilities Source
> externals/gridflow
> externals/sc4pd/source
> iemlib/src/iem_mp3

I cannot find much that is not Pd-related there. flext is not
importing sndobj and stk, gridflow is not mirroring Ruby, SC4Pd is not
the same as Supercollider and Gem doesn't include Quicktime. 

Take for example the Csound repository: To build e.g. the
fluidsynth-opcodes, Csound expects to find the fluidsynth sources or a
symlink in a certain place. However the fluid-sources are not
duplicated into the CVS, no parallel version of fluidsynth is created.
Instead the package maker is responsible for doing so and if the
sources aren't there, the opcodes will not be built. 

For dssi~ and fluid~ it's even easier, as the source code is never
necessary to built these externals.

Ciao
-- 
 Frank Barknecht                 _ ______footils.org_ __goto10.org__