[Qt-interest] LGPL and static linking

Justin McPherson justin.mcpherson at nokia.com
Thu Dec 3 06:31:39 CET 2009


QtMultimedia was developed in house and is presumably released under  
all the licenses that Qt is released under.

- Justin

On 02/12/2009, at 1:10 AM, ext Raul Metsma wrote:

> Same question also here and count modules QtHelp and QtMultimedia  
> also in.
>
> Raul Metsma
>
> Christian Dähn 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
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest





More information about the Qt-interest-old mailing list