[Development] Licensing of qtbase
felix.crazzolara at gmail.com
Sat Jul 16 12:00:33 CEST 2022
I wanted now to write some CMake code to ensure that Qt is always and
entirely linked dynamically. For that purpose, I intended to iterate
through the target properties LINK_LIBRARIES and INTERFACE_LINK_LIBRARIES
of Qt5::Widgets or Qt6::Widgets and check that all dependencies resolve to
shared libraries eventually.
I have now two questions. First, is there some existing code in the Qt code
base that does what I want already?
Secondly, I noticed that an interface dependency of Qt6::Widgets is
Qt6::CoreQt6::Gui and if I check whether Qt6::CoreQt6::Gui is a target with
"if (TARGET Qt::CoreQt6::Gui)", it turns out that it is not. This confused
me since it doesn't seem like a valid library name to me. How can I resolve
Qt6::CoreQt6::Gui to an absolute file path?
On Wed, 13 Jul 2022 at 14:00, Felix Crazzolara <felix.crazzolara at gmail.com>
> Thank you very much for your explanations Allan and Florian.
> On Wed, 13 Jul 2022 at 13:32, Allan Sandfeld Jensen <kde at carewolf.com>
>> On Mittwoch, 13. Juli 2022 12:14:27 CEST Felix Crazzolara wrote:
>> > Dear everyone,
>> > I would like to use Qt for a personal project. In my project, I use a
>> > relatively small part of Qt and I think that the components of QtBase
>> > https://github.com/qt/qtbase
>> > suffice for my application.
>> > I read about the Qt licensing model on the official website. What
>> > me now to see, is that there are quite a few licenses in the LICENSES
>> > folder in the repository referred to above. Among them is for example an
>> > MIT license.
>> > How can I understand this? Is the QtBase component of Qt itself licensed
>> > with an MIT license? Can I choose which license in the LICENSES folder
>> > use if I restrict myself to QtBase?
>> No, you can only choose between LGPLv3, GPLv2 or commercial, you have to
>> compatible with one of those. The MIT license is a license for components
>> itself uses, and shouldn't affect you.
>> Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development