[Qt-interest] LGPL and static linking

Bastian Bense bastibense at gmail.com
Wed Nov 25 10:32:54 CET 2009


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



Am 25.11.2009 um 10:09 schrieb Stefan Josefsson:

> I am planning to develop a commercial closed source application on top of Qt/E and would like to use Qt statically linked to my application as this gives a substantial boost to the startup time and also reduces the RAM usage. The question is whether I am allowed to use the LGPL license of Qt. I have read a number of discussions about LGPL and static linking and some say that it is not allowed (those that know a little bit less?) and some say that it is allowed (those that know a bit more?) as long as you provide the rest of the world with a way to recompile the application with a modified version of the LPGL:d code (Qt in this case). See for instance these links: 
> http://www.gamedev.net/community/forums/topic.asp?topic_id=541047 
> http://www.ics.com/files/docs/Qt_LGPL.pdf 
> http://ubuntuforums.org/showthread.php?t=1066632 
> 
> What is Nokias view of static linking and LGPL? 
> 
> I also just read on the blog that the QtScript module from now on will be under LPGL even if you buy a commercial license of Qt, so a commercial license is not the solution for using static linking with Qt if you want to use QtScript. 





More information about the Qt-interest-old mailing list