[Development] Licensing of qtbase

Tino Pyssysalo tino.pyssysalo at qt.io
Thu Aug 4 07:56:14 CEST 2022

On 3.8.2022, 15.21, "Development on behalf of Benjamin TERRIER" <development-bounces at qt-project.org<mailto:development-bounces at qt-project.org> on behalf of b.terrier at gmail.com<mailto:b.terrier at gmail.com>> wrote:

On Wed, 13 Jul 2022 at 13:05, Florian Bruhin <me at the-compiler.org<mailto:me at the-compiler.org>> wrote:

https://www.qt.io/product/features?hsLang=en#js-6-3 lets you see the
individual components of Qt and what license they are available as.

> That's some high level of FUD and BS.
> If I select LGPLv3, all Qt tools are greyed out (moc, qmake, Qt Creator, etc.).
> Sure these tools are themselves not licensed under LGPLv3, but nothing prevents them from being used for LGPLv3 projects.

Indeed. If using means running here, GPLv3 sets no limitations for running the unmodified version of the SW. Limitations are related to the modified SW. And GPLv3 is compatible with LGPLv3, but then the combination will be GPLv3-licensed.

I did not put these license details on the features page. Small clarification would not hurt.

> Ang given the text at the top of the page:
Please select a [...] license model, [...] programming language to see, what items are available for that selection.
> it will clearly make some people think that one cannot use these tools with LGPLv3 projects.
> Especially because when selecting a language it will filter based on which languages can be used with a tool, not which languages a tool is developed with.

I agree this is a little bit counter-intuitive. In one place we talk about development licenses and in another place using the SW. I will try to clarify this.

Tino Pyssysalo
Maintainer of Qt features page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20220804/0ca2fd00/attachment-0001.htm>

More information about the Development mailing list