Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
On 6/20/22 11:58 PM, Thiago Macieira wrote: Looks like a mistake, probably simple copy & paste one. I've submitted a licence fix for these two files: https://codereview.qt-project.org/c/qt/qtwayland/+/417519 I don't own the copyright on them. Let's see what Qt Company says. Thanks for submitting that fix, looking at the update from Volker it appears this was indeed an error. I appreciate all your help on this, Thiago (+ Qt folks for reviewing and approving the patch)! Cheers, Mike ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
On Monday, 20 June 2022 16:24:43 PDT Mike Rochefort wrote: > Looking at the source, I did a quick scan of the repository to see what > was LGPL and GPL based. Your description of the situation was pretty > spot on, Thiago, though there are two files in the client project that > are GPL licensed. These files are new in Qt 6.3; they don't exist in any > version of Qt prior (including 5.15) and were added in the following > commit: d89c892 > > Scan results: https://gitlab.com/-/snippets/2353685 Looks like a mistake, probably simple copy & paste one. I've submitted a licence fix for these two files: https://codereview.qt-project.org/c/qt/qtwayland/+/417519 I don't own the copyright on them. Let's see what Qt Company says. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
Looking at the source, I did a quick scan of the repository to see what was LGPL and GPL based. Your description of the situation was pretty spot on, Thiago, though there are two files in the client project that are GPL licensed. These files are new in Qt 6.3; they don't exist in any version of Qt prior (including 5.15) and were added in the following commit: d89c892 Scan results: https://gitlab.com/-/snippets/2353685 Examining the cmake config for the client project, those two shell integration files are included in the WaylandClient module's sources (lines 51 and 52). As I mentioned previously IANAL, but would these sources files have the impact of GPLing the QtWayland client library? How Qt likes to handle the "not-really-meant-for-public-use" APIs is a bit beyond me. Cheers, Mike ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
On Thursday, 16 June 2022 15:23:02 PDT Mike Rochefort wrote:
> In terms of bundling with the rest of the Qt framework, you're saying
> just the following artifacts from a build are needed? I don't know if
> any other objects or resources from the QtWayland package are necessary.
>
> - libqwayland-{egl,generic}.so
> - libqwayland-xcomposite-{egl,glx}.so (optional for Qt5?)
> - libQt{5,6}WaylandClient.so.{5,6} (linked by the above objects)
I believe so, yes.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Cloud Software Architect - Intel DCAI Cloud Engineering
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
On 6/16/22 5:52 PM, Thiago Macieira wrote:
The Wayland *client* library API and the wayland QPA plugin, which are
licensed
LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only
which is the same as qtbase, see
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/global/qglobal.h
And the Wayland compositor (server) library API, which is licensed
LicenseRef-Qt-Commercial OR GPL-3.0-only
If you just want your application to run in a Wayland session, you need the
client library and plugin only.
This is good to know. I don't know what I was looking at last week, but
I could have sworn when I was going through the code last week I saw
some disconnects between the license headings in the qt/qtwayland repo.
Good reason to not look at code late at night! Looking at it again today
things seem to line up with your information. Is this explicitly
documented anywhere outside of the code headings? From what I could find
in the Qt docs the only license mentions are around the compositor and
integration plugin:
=== https://doc.qt.io/qt-6/qtwaylandcompositor-index.html
Qt Wayland Compositor and the Qt Wayland integration plugin are
available under commercial licenses from The Qt Company.
In addition, Qt Wayland Compositor is available under the GNU General
Public License, version 3, while the Qt Wayland integration plugin is
available under the GNU General Public License, version 3 or the GNU
General Public License, version 2.
===
In terms of bundling with the rest of the Qt framework, you're saying
just the following artifacts from a build are needed? I don't know if
any other objects or resources from the QtWayland package are necessary.
- libqwayland-{egl,generic}.so
- libqwayland-xcomposite-{egl,glx}.so (optional for Qt5?)
- libQt{5,6}WaylandClient.so.{5,6} (linked by the above objects)
Cheers,
Mike
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
Re: [Interest] Impact of QtWayland licensing on applications bundling OSS Qt?
On Thursday, 16 June 2022 11:20:55 PDT Mike Rochefort wrote: > Additionally, considering Wayland is becoming a core piece of the Linux > ecosystem is there a reason why the QtWayland module doesn't follow the > same licensing as QtBase where the other QPA plugins are provided? The module has two parts with different licensing: The Wayland *client* library API and the wayland QPA plugin, which are licensed LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only which is the same as qtbase, see https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/global/qglobal.h And the Wayland compositor (server) library API, which is licensed LicenseRef-Qt-Commercial OR GPL-3.0-only If you just want your application to run in a Wayland session, you need the client library and plugin only. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
