[Qt-interest] LGPL and static linking

[Bastian Bense]

QtScript is licensed under the LGPL just like the rest of Qt 4.6.

You are allowed to use it in commercial/closed source applications as long
as you don't link statically/embed it without providing the object files
(from what I've learned on this thread).

Personally I don't see such a big problem with dynamic linking. It might
take a bit longer, but on the long run it gives you more freedom to upgrade
the Qt libs without having to re-compile. Simply create an installer for
Windows which places the required Qt libs into the application directory;
use macdeployqt on Mac OS X.



2009/11/25 Christian Dähn <daehn at asinteg.de>

> Hi,
>
> > I'm also worried about the GPL/LGPL move.
> > I have QT license exactly for that, static linking.
> > But Trolls are adding modules which I am not able to use
> > (QtMultimedia/phonon, Webkit, QtHelp, now the QtScript)
> > which makes me worried
>
> I aggree to that - I'm in the same situation:
> Commercial license but many parts of Qt now don't allow
> to use it for closed source development.
>
> Currently I'm worried that a commercial license doesn't
> bring me any advantages - but more problems and lesser
> possibilities to create closed source applications.
>
> Further I have to decide, if it's possible for our company
> to use Qt 4.6 in the future - due to the change of QtScript
> which cannot be used in commercial apps any more :-(
>
> So: Qt 4.6 will bring many many disadvantages for commercial
> developers - so why buy licenses any more?
>
> --
Best regards,
Bastian Bense
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20091125/f2f91221/attachment.html