On Thu, 23 Aug 2001, Andreas Beck wrote:
> > > > 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.
Hopefully this is not what Debian wants -- what makes most sense
for Debian is to build libraries/sublibs that are statically linked against
everything else (libc/xlib/etc) but still are dynamically loaded by
a statically linked libggi (which is statically linked to libgii/libgg).
That is, assuming a staticly linked library _can_ dlopen (?)
I cannot believe we are the first software package to chafe against
this Debian policy. There must be other highly modular libraries
that cannot be truly made into statics.
--
Brian
