Re: [Audacity-devel] LV2/LADSPA library summary
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
|
From: George F. <faz...@gm...> - 2008-07-08 16:02:58
|
Hello Lars, I wouldn't like to influence your decision too much (mainly since my understanding of the internals and dependencies of these libraries is still limited), but I have a small note. If the semantic-web world really takes off there might be interest to use these libs for other purposes too. As an example I already compiled them with audacity to extended the metadata editor and they might become part of the Vamp plugin support as well. I think it would be best to have the most general solution possible since Redland, Rasqual and Raptor support quite different though sometimes overlapping functionality. My main (less related) question really is whether static linking is there to stay in the long term? (I used them installed as system libraries on os/x which worked just fine.) George On Jul 8, 2008, at 8:48 AM, 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. 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. > > Any thoughts? > > There is also the possibility of doing away with LRDF altogether and > just use Redland for that too - LRDF is really just a wrapper that > adds > a LADSPA-specific API. But I'd like to focus on getting LV2 working > right first. > > > --ll > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08_______________________________________________ > audacity-devel mailing list > aud...@li... > https://lists.sourceforge.net/lists/listinfo/audacity-devel |