Nathaniel McCallum wrote:
> > The concern that I (as a libcurl user, not a committer) have with this
> > is that an app can't link statically with LGPL libs unless it is also
> > *GPL. I currently link statically with libcurl, so if in some way
> > libcurl became tightly enough bonded with libproxy that I couldn't do
> > static links any more, that would be a big problem.
>
> Does this also mean that you need to statically link to *both* libcurl
> and libproxy? Because you could still do a static link to libcurl and
> a dynamic link to libproxy.

Nothing to do with Mohun's problem, but a bit of information:
On some embedded targets, static linking is the only option; there is
no dynamic linking. This may affect your approach to "plugins" too,
as there's no run-time "dlopen()" style linking either.

-- Jamie
Received on 2007-12-27