2011/2/26 Olivier Guilyardi :
Ah, didn't know. :-) Never actually used the NDK, only the SDK.
> The only way to know what size it will really take is to compile with the
Ah sure, static linking would cut out some unneeded code too. Don't
really know how much actually.
> I haven't played so much with flags such as -Os because there's like a very very
This depends on what you are using it for and how. Being decentralized
& extensible, you could also use it to make coffee. :-)
> I don't want to wake up old trolls, but last fall, when I had a sound engineer
> So most logically, when time comes to add plugin support, I will start with
I respect your choice and understand the rationale. Also, all of this
changes won't happen by tomorrow (my guess is 2/3 months, based on
feeling more than facts), so if you "need effects soon", you should
probably go that route.
However, in the long run, I would avoid LADSPA for two reasons: 1.
lack of extensibility, etc., 2. LADSPA plugins can run into LV2 hosts
without explicit support through the NASPRO bridges (which will be
able to work by default with SLV2 starting from the next SLV2 release,
otherwise you can grab the current svn SLV2 already).
So it turns out it depends on how long you want to wait, or rather if
you would consider giving some help, and what you want to do with LV2.
Linux-audio-dev mailing list