[PD] how do I build plugin~ from the CVS repo?

Hans-Christoph Steiner hans at eds.org
Wed Dec 6 19:56:47 CET 2006


On Dec 6, 2006, at 9:15 AM, Jamie Bullock wrote:

>
> Hi Hans,
>
> On Tue, 2006-12-05 at 11:14 -0500, Hans-Christoph Steiner wrote:
>> FYI, I just enabled the building of [plugin~] on Mac OS X.  So it
>> should be included in nightly builds and upcoming test and final
>> releases.
>>
>
> Any chance of getting [dssi~] included in this? It has an additional
> dependency on the liblo library, but it builds and works fine on both
> linux and Mac OS (powerpc and intel).
>
> The advantages of [dssi~] over [plugin~] are
>
> 1. It supports DSSI plugins as well as LADSPA
> 2. It can host multiple plugin instances within a single [dssi~]
> instance e.g. [dssi~ sine_faaa 20] for 20 sine oscillators.
>
> It doesn't do VST but other than that the functionality of plugin~  
> is a
> subset of the functionality of dssi~.

Sure, if you do the work. I think the issue was that the DSSI code  
would have to be maintained in the pure-data CVS, which some people  
strongly protested.  DSSI isn't in Fink.  In order for it to be  
supported in the auto-builds and Pd-extended packages on Mac OS X,  
the code either needs to be in CVS or Fink, or included in the OS.

You could just make a libdir package, then people could use DSSI with  
plain pd too (with the libdir external).

.hc


------------------------------------------------------------------------

Looking at things from a more basic level, you can come up with a  
more direct solution... It may sound small in theory, but it in  
practice, it can change entire economies.     - Amy Smith






More information about the Pd-list mailing list