> > > Do you really mean Debian wants every single LibGGI target, renderer,
> > > and extension lib all rolled into one .a?
> My thought is that a static library would contain debugging information so
> that could solve two problems at once. (Or am I wrong here?)
Dynamic libs can also contain debug infos - no problem.
The problem about having a static version of LibGGI is that it will still
try to dynamically load the .so driver files which are dynamic libraries
basically.
The only way to really statically link a LibGGI program would be, if all the
targets would be rolled into the executable and then accessed by a
table-lookup-call or similar.
LibGGI has been prepared to do this, but noone has yet written the code
for making up such a table and using it.
It's a lot of work probably for a very rare application.
but if someone likes this challenge, go for it.
CU, Andy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
