Subject: RE: [linux-audio-dev] LADSPA Update (http://www.ladspa.org)
From: Richard W.E. Furse (richard_AT_muse.demon.co.uk)
Date: Sun May 21 2000 - 19:25:47 EEST
The situation isn't so bad: a C host need do nothing special to run a C++
plugin.
On the other hand, to make this work a C++ *plugin* needs to be careful to
provide all the necessary links to external libraries in order to work
correctly when used by the host. There is a problem here, as there may be
different C++ library versions on other machines. Essentially a binary of a
C++ plugin will or will not work on a particular host machine depending on
whether or not the relevant C++ library version is present. An easy way to
check this is to call analyseplugin on the plugin file.
These same issues apply to any ladspa plugin which uses an external library
beyond the standard C and maths library allowed in ladspa.h.
-- Richard
-----Original Message-----
From: Benno Senoner [SMTP:sbenno_AT_gardena.net]
Sent: Sunday, May 21, 2000 4:02 PM
To: Kai Vehmanen; linux-audio-dev_AT_ginette.musique.umontreal.ca
Cc: ecasound-list_AT_wakkanet.fi
Subject: Re: [linux-audio-dev] LADSPA Update (http://www.ladspa.org)
[...]
Sorry I am a bit lost in this whole running C++ plugins within a C host.
Can someone please post a quick summary of the situation here:
-What are the correct steps that a C host must take in order to be able to
run
C++ plugins.
-(exact linking options or runtime loading of C++ libs etc)
- eventual special programming guidelines
This should REALLY go into the official LADSPA documentation, so that
we might save some trouble later, because suddenly we will have
10 LADSPA C-host developer complaining that the kickass-foobar C++
plugin doesn't run on their hosts.
Benno.
This archive was generated by hypermail 2b28 : Sun May 21 2000 - 19:50:23 EEST