Nice, I didn't get any response before so I haven't worked on it.
It's still a hack - but with potential... To make it build I had to switch from automake which only complicated things, and instead use a smarter autoconf file. I don't use windows so that part should be broken.
I think plugin~ is badly designed since it is tailor made for the different plugin architectures - hiding the complexity from the user in a bad way. VST and LADSPA are different, and since OS X have both, which one should plugin~ use? I guess the same thing would apply to windows if anybody cared to port LADSPA to it. The obvious solution(in my world) is to drop VST and rename plugin~ to ladspa~. It would enable portable patches(which was my motivation in the first place), - if the ladspa plugins were ported to different platforms then the patch using ladspa~ would use exactly the same plugin architecture and look for the same plugin on that platform...
I have the changes on another machine but I'll send them later, it's just a new configure.in and makefile.in and I think some small changes to plugin.h(to use autoconf). To build on OS X fink and the ladspa packages is probably needed...
/Z
fre 2005-02-18 klockan 00:10 -0500 skrev james tittle:
On Dec 29, 2004, at 2:50 PM, Zachris Trolin wrote:
I've just managed to have [plugin~] compile with LADSPA support on OS X by trying to figure out the correct flags from other externals and hacking automake. I asked on the userlist some weeks ago but got no answer so I had to do it myself.
Right now all automake files are in a mess but atleast it compiles and it's possible to load the external and use it without problem. If anybody else needs this mess I'll gladly share it :)
...great to hear! I know it's been awhile, but I've just recently been trying compile this external, and am stuck with configure not being able to identify my build system :-(
...did you put this up anywhere? I think it'd be better at this point to update the cvs so that others can build this too...
I'd love to see a working plugin~ ship with the OS X distributions of pd If nobody else wants to do it I'll try to fixup the makefiles so that it should work for most architectures.
...what's the status on this? I think it'd be great to compare notes...
thanx, jamie
I think plugin~ is badly designed since it is tailor made for the different plugin architectures - hiding the complexity from the user in a bad way. VST and LADSPA are different, and since OS X have both, which one should plugin~ use? I guess the same thing would apply to windows if anybody cared to port LADSPA to it. The obvious solution(in my world) is to drop VST and rename plugin~ to ladspa~. It would enable portable
another solution could be rename grrrrr's VST~ to plug~ and add DSSI/AU/LADSPA/etc support, since it is by far the best one out there but only runs on windows.. afaik the other ones cant even currently do the basics like query a plugin for all accessible paramaters..
at least thats what i'd do if i could code c++ and wanted to switch to mac or linux.. c