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
