[Qt-interest] LGPL and static linking

[Philippe]

Naive position maybe, but If you distribute or produce the exact same
application in 2 forms: with shared libraries, and statically linked (with
strictly the same features), then you give "the proof" (to whoever needs it)
that your application is not a a "derivative work".

Philippe


On Tue, 1 Dec 2009 16:06:16 +0100 (CET)
Christian Dähn <daehn at asinteg.de> wrote:

> Robin Helgelin <lobbin at gmail.com> wrote:
> >
> > What about Webkit? I was told that as Webkit is LGPL, I'm not able to
> > static link to Webkit even though I have a commercial license of Qt.
> > If this also happens with QtScript, it means that all licenses becomes
> > unusable for us if we still want to use the whole Qt stack.
> 
> Exactly! We as company have the same problems:
> Why to buy a commercial license for a toolkit where it's licenses
> forbid the usage in commercial / closed source applications.
> 
> @QT / NOKIA:
> How to solve the problems with the QtScript + WebKit LGPL licenses
> in commercial applications where static linking is needed -
> or better: where the customer doesn't have a chance or isn't allowed
> to use shared libs?
> 
> I already asked this question before by an eMail to the sales team
> last week - but nobody in a huge company like Nokia has time or is
> willing to answer a commercial customer (like me).
> 
> Best Regards,
> Chris
> 
> 
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest