CaROS/meta-qt6
3
0
Fork 0
mirror of http://code.qt.io/yocto/meta-qt6.git synced 2026-01-01 13:58:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
411 Commits 71 Branches 133 Tags 7.2 MiB
BitBake 73.2%
C++ 10.8%
PHP 5.5%
Clojure 3.8%
HTML 3.3%
Other 3.4%
9de3ec80dc
Go to file
Samuli Piippo 9de3ec80dc SDK: make sure initial qt host path is absolute 
__qt_toolchain_initial_qt_host_path is assigned to QT_HOST_PATH and then
to CMAKE_FIND_ROOT_PATH. Problems occurs if that path is relative.
CMake doesn't do relative path resolving by default in find_package,
when doing sub-prefix checking between find root path and prefix path.

Patch the qt.toochain.cmake so that it always uses absolute path for
__qt_toolchain_initial_qt_host_path, but make it still based on its
own location.

Fixes: QTBUG-103818
Change-Id: I1cce126c243c017b1cecd14a0fd616cb0328fe6d
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
(cherry picked from commit ea541e308f)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2022-06-06 21:14:50 +00:00
classes sdk: Use correct CMAKE_PREFIX_PATH for Qt modules 2022-05-18 13:02:00 +00:00
coin Update handling of commercial modules 2022-05-23 05:07:32 +00:00
conf Update handling of commercial modules 2022-05-23 05:07:32 +00:00
licenses Update The-Qt-Company-Commercial 2022-03-24 19:51:55 +00:00
recipes-devtools/python python3-antlr4-runtime: use correct recipe name 2022-04-07 19:28:00 +00:00
recipes-qt SDK: make sure initial qt host path is absolute 2022-06-06 21:14:50 +00:00
COPYING.MIT initial commit 2020-01-24 11:54:52 +02:00
README.md Update handling of commercial modules 2022-05-23 05:07:32 +00:00

README.md

Qt6 OpenEmbedded/Yocto Project layer

This layer depends on:

URI: https://git.openembedded.org/openembedded-core/

and optionally:

URI: https://git.openembedded.org/meta-openembedded/

Yocto version support

The branching of meta-qt6 layer follows Qt branching scheme, that is dev for the development branch, 6.x for each minor release and lts-6.x for commercial LTS releases.

Following table shows the Yocto branches which are used to test each Qt version (x) and any additional Yocto releases that are stated in the LAYERSERIES_COMPAT (c).

Yocto \ Qt 6.3 6.2 6.1 6.0
kirkstone x x
honister x x
hardknott c c x x
gatesgarth c c x x
dunfell x x x x

Commercial Qt

Qt is dual-licensed under commercial and open source licenses. The license can be selected using the QT_EDITION variable. commercial and opensource are valid values. The default value is opensource.

For commercial Qt users, the layer provides additional support with LTS (Long Term Support) releases for selected Qt versions and additional Qt modules licensed as commercial-only.

The LTS releases are available in branches named lts-6.x. The source code for the LTS releases and the commercial Qt modules are only available for commercial Qt license holders. They can only be built and used if you have a commercial Qt license and you have set up SSH access to Qt Gerrit (see links below).

The commercial Qt modules are included in the build if the QT_COMMERCIAL_MODULES variable is set to 1 and you are using a commercial edition of Qt.

QtWebEngine

QtWebEngine needs at least CMake 3.19, which is available starting from Hardknott. For this reason QtWebEngine is not tested on older releases.

Contributing

To contribute to this layer you should submit the patches for review using Qt Gerrit.

More information about Qt Gerrit and how to use it:

Layer maintainers