Re: [Audacity-devel] LV2/LADSPA library summary

[Richard A. <ri...@au...>]

On Tue, 2008-07-08 at 09:48 +0200, Lars Luthman wrote:
> I'm planning to add the rest of the libraries needed for LV2 support
> today, and I'd like to know what way people think would be best to do
> it. The libraries needed are
> 
> FOR LADSPA CATEGORIES: LRDF, which depends on Raptor
> 
> FOR LV2: SLV2 which depends on librdf which depends on Raptor and Rasqal
> 
> My original plan was to have each as a separate library in lib-src, with
> separate user control for using system/local copies of each (with
> autoconf), but now I'm thinking it would be better to group Raptor,
> Rasqal and librdf as one single Redland conglomerate that is treated as
> a single library in the way that all three either need to be installed,
> or all three are built from local source. It would reduce the number of
> extra libraries from 5 to 3, which is good, while it would add some
> redundant code and link dependencies for users who just want LADSPA
> categories and not LV2 support, which is bad.
I'm inclined to agree that the reduced complexity and reduced number of
possible configurations outweighs the extra dependencies.

> But if we do have Redland
> as a single library we could maybe add some configuration options later
> that determine which parts of it gets built depending on whether LRDF
> and/or SLV2 are going to be used.
I'm not sure it's worth the effort. I wouldn't intend to package any of
these libraries into the source tarballs for builds on Linux - they
should just be using the system libraries. For distributed builds on
Windows and OS X both will be enabled anyway, so there is no real
incentive to mess around with lots of configure options that won't
really get used.

Richard