[Qt-interest] LGPL and static linking

[Dan Milburn]

Christian Dähn wrote:
> Andreas Pakulat <apaku at gmx.de> wrote:
>>> 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?
>> Then don't use QtScript and Webkit. Its not possible to change the license
>> of Webkit, unless you talk all Webkit-developers into changing their minds
>> about the license. So there's nothing that Nokia can do there. For
>> QtScript: the old QtScript implementation is still available as a Qt
>> solution under the old license.
> 
> Thanks for your answer. It would be great, if I wouldn't have the
> problems of using static binaries and if the performance optimizations
> of the new QtScript module weren't needed.
> 
> Summing up the Qt toolkit was changed in a way where longterm 
> commercial customers get problems with open source licenses and 
> nobody took care of that.
> 
> Such was completely incredible in the past - where Qt was developed
> by Trolltech - not by Nokia.

I'm fairly sure development on QtWebkit started before Nokia acquired 
Trolltech.

What could Trolltech have done?  Webkit wasn't developed by them.  They 
wouldn't be able to relicense to Qt Commercial customers any more than 
Nokia can.

I can agree that lack of response to your queries about this is a 
problem, but it wouldn't change the situation.

Dan