[Qt-interest] LGPL and static linking

[alexander golks]

as far as one reads:

"Alternatively, a statically linked library is allowed if either source code or linkable object files are provided."

thus, if i give the source or linkable objects files, that "load" the static libs,
and not the whole closed source of my programm,
this would suffice the lgpl terms?
e.g. if i write a "LPGL wrapper loader" for the statically linked qt dll,
this would be safe?
but in turn, the speed and memory efforts are null and void,
cause this wrapper must be a dll, too?
what if i allow my wrapper to be linked statically? 
like here: http://en.wikipedia.org/wiki/GPL_linking_exception

you see, i've tried to understand this gpl, lgpl, etc. stuff, 
and in germany lawyers tend to argument in different ways about this all.
furtheron, as far as i know, no court in germany has yet delivered a judgment 
in this special case.

after all, one must consult a lawyer to get on the safe side, whatever was written here...

Am Wed, 25 Nov 2009 10:33:56 +0100
schrieb qt-interest-request at trolltech.com:

> LGPL only allows for dynamic linking of the Qt libraries. If you want static linking, you can switch to GPL (probably not what you want), or get a commercial license.
> 
> http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License
> http://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License#Differences_from_the_GPL

-- 
/*
 *  fs_dprintk (FS_DEBUG_IRQ, "Iiiin-coming (0)!!!!\n");
 *          linux-2.6.6/drivers/atm/firestream.c
 */
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20091125/92eb9658/attachment.bin