On Tue, 25 Jul 2006, Bill Janssen wrote:
Note that plugins themselves are shared libraries; it wouldn't take much to
extend the plugin API to include a function to allow plugins themselves to
load other shared libraries, as long as they do so before trying to look at
(or use) the plugin
Jonathan Gordon wrote:
what about loading the static libraries into the codec or audio
buffer? it would mean no audio in those plugins, but would add heaps
of functionality.
That is a solution, but I still don't understand why it would be a
problem to link statically.
Linus
Exactly, just link the library statically to the plugin. Sure each plugin
using the lib would drag around it's own copy of it, but disk space is the
only thing a DAP has plenty of.
Yes, that's what I'm doing now. Works fine, except that you have
multiple copies of the code.
Note that plugins
I've been working on some Rockbox browsers for ebooks, targeting the
G5 iPod. They use standard libraries, like libpng and zlib. I've
developed rockbox-able versions of these, and would like to bundle
them up as shared libraries instead of statically linking them into
each plugin. Is there any
On Mon, 24 Jul 2006, Bill Janssen wrote:
would like to bundle them up as shared libraries instead of statically
linking them into each plugin. Is there any standard way to do this with
Rockbox? Does it even have the idea of shared libraries which applications
(plugins) use?
No, they have
