Building Qt modules uses extra CMake instructions that try to be clever
about which CMAKE_PREFIX_PATH to use. With SDK, these instructions end
up using the SDK host paths in the device instead of the actual device
paths. Add CMake option to prevent Qt from changing the default prefix.
Fixes: QTBUG-103577
Change-Id: Ia933c843d811e6adb2ed4ede4708f55a6f0e8f0c
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit
|
||
|---|---|---|
| classes | ||
| coin | ||
| conf | ||
| licenses | ||
| recipes-devtools/python | ||
| recipes-qt | ||
| COPYING.MIT | ||
| 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 LTS (Long Term Support) releases
for selected Qt versions. These are available in branches named lts-6.x.
The LTS versions 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).
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
- Samuli Piippo samuli.piippo@qt.io