Company
Nokia add LGPL to Qt Licensing Model
Image

Nokia today announced that its Qt cross-platform user interface (UI) and application framework for desktop and embedded platforms will be available under the open source LGPL version 2.1 license from the release of Qt 4.5, scheduled for March 2009.

When released in March 2009, Qt will be made available under three licensing options: Commercial, LGPL and GPL.

 

 

In addition:

  • Qt source code repositories will be made publicly available and will encourage contributions from desktop and embedded developer communities.
  • Service offerings for Qt will be expanded to ensure that all Qt development projects can have access to the same levels of support, independent of the selected license.

By offering Qt under LGPL version 2.1 license terms alongside today’s licensing options Nokia hopes to:

  • Facilitate wider adoption of Qt across industries, desktop, web and embedded platforms
  • Establish Qt as a de facto standard for application development
  • Receive more valuable feedback and increased user contributions to ensure that Qt remains the best-in-class, cross-platform framework
  • Extend Nokia existing platform commitment to the open source community

What is the difference between LGPL and GPL?

Both of these licenses are complex documents that require careful reading to appreciate the significant differences between both licenses. However a high-level explanation is that the GPL requires that any derivative work (e.g.: applications developed using Qt) must be relicensed under the terms of the GPL. The LGPL is less restrictive and enables the development of closed source applications. We will be releasing Qt under the LGPL version 2.1 license, plus continuing to offer Qt under the GPL version 3.0.

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.

Read More