Linked by Thom Holwerda on Wed 14th Jan 2009 09:54 UTC, submitted by Almar
Qt After Nokia purchsed Trolltech last year, doubts arose about how Nokia would handle the dual licensing model of Qt, the advanced cross-platform toolkit which lies at the base of the KDE Free software desktop. As it turns out, these doubts were unfounded, as Nokia today announced it's going to add the LGPL to Qt's licensing model, starting with Qt 4.5.
Thread beginning with comment 343467
To read all comments associated with this story, please click here.
Restrictions
by czubin on Wed 14th Jan 2009 13:32 UTC
czubin
Member since:
2005-12-31

I'm wondering what all the restrictions left are - if one would choose LGPL above commercial license - for developing a closed application.

* You cannot staticly link Qt(who want a big binary?) only dynamicly.

* You cannot go from LGPL to Commercial license.

Any other restrictions? Or does this somewhat sum it all up?

RE: Restrictions
by FunkyELF on Wed 14th Jan 2009 13:47 in reply to "Restrictions"
FunkyELF Member since:
2006-07-26

Yeah, I was wondering the same thing. What are the advantages in getting a commercial license?

You mentioned only being able to link dynamicly. I can't think of much more.

If you have a commercial license I guess you could change the Qt Source code without contributing your changes back.

Reply Parent Bookmark Score: 2

RE[2]: Restrictions
by minio on Wed 14th Jan 2009 14:00 in reply to "RE: Restrictions"
minio Member since:
2006-05-14

From QTsoftware FAQ:
Why would I want to buy a commercial license? What is the difference?

The commercial Qt license includes email support, access to upgrades and allows you to develop fully closed source software. The LGPL carries some restrictions regarding the ability for users to relink libraries and other restrictions that may impose architectural requirements that some organizations might not be comfortable with.

So it looks like Nokia also can't think of much more ;)

Reply Parent Bookmark Score: 4