[collectd] Static Build

[Florian Forster]

Hi Jesse,

On Fri, Jun 13, 2008 at 08:33:29AM -0700, Jesse Dutton wrote:
> They use a macro to expose a static module_register function when the
> module is not built-in. In the built-in case, we could mangle the
> function names so that they are unique, and use the HAVE_PLUGIN_X
> #defines to call each module_register in turn during startup.

linking everything together to one static package is basically the only
option in that case. Statically linking libraries into shared objects is
problematic - especially under non-x86 architectures.

Using some magic to enable static linking of plugins into the daemon
will introduce a lot of code complexity, I guess. But if you make a
schematic but technical suggestion[*] how you would implement this we
can probably talk about this in a far more constructive way..

Regards,
-octo

[*] By that I basically mean simplified pseudo-code ;)
-- 
Florian octo Forster
Hacker in training
GnuPG: 0x91523C3D
http://verplant.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20080616/bd4cf9cd/attachment-0001.pgp