There is a static component that is linked when linking to dynamic
libraries, however that is present mostly to inform the compiler on what the
ABI is, or how your compiled code is expected to interact with the DLL. It
is very possible to write a piece of code that explicitly loads the library
by name and manually builds calls to it. In fact, it's likely possible to
compile a program intended to run with a .dll without any related files
being on the machine at the time.
On Thu, Oct 28, 2010 at 8:52 AM, Carlo Wood <ca...@alinoe.com> wrote:
> On Thu, Oct 28, 2010 at 08:27:52AM -0500, Dave Booth wrote:
> > On 10/28/2010 06:29, Carlo Wood wrote:
> > <snip>libmedia_plugin_webkit.{sp,dll,dylib}<snip>
> >
> > Make sure you quote examples of static linking when you're talking about
> > static linking :)
>
> Make sure you read carefully what I say and understand it before
> talking about wrong examples :)
>
> libmedia_plugin_webkit.{sp,dll,dylib} are linked STATICALLY with
> the Qt libs (as in, linked with .a).
>
> Thus:
>
> Qt*.a (LGPL) + LL*.o (LGPL+FLOSS) = libmedia_plugin_webkit.so
>
> ==> LL*.o must be made public (or their source code), or
> libmedia_plugin_webkit.so cannot be shipped.
>
> --
> Carlo Wood <ca...@alinoe.com>
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting
> privileges
>
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
