Go to file
Samuli Piippo fcee8bec25 qtgrpc: workaround kirkstone build
QtGRPC now support only cmake-built protobuf, which causes builds
on kirkstone to fail, since it doesn't provided needed CMake support.
Add workaround so that toolchain builds can still be done, even though
it won't have support for GRPC tools.

Change-Id: Ica8d289b01f7c5856f5d42e26b810cd3adc78722
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
2024-10-29 14:04:39 +00:00
classes Remove TMPDIR references from qmake files 2024-10-18 12:48:06 +00:00
coin coin: add workaround for clang build 2024-10-18 12:48:47 +00:00
conf Bump version to 6.9.0 2024-06-13 16:04:15 +03:00
licenses qt6: update licenses 2022-06-03 09:06:56 +00:00
recipes-core Support SDK workflow inside a Yocto build 2023-01-11 14:45:27 +00:00
recipes-devtools/python Remove webengine related GCC13 patch 2024-10-25 06:52:14 +00:00
recipes-multimedia/webp libwebp: add workaround for native build 2024-02-06 07:11:09 +00:00
recipes-python/pytest-qt pytest-qt: upgrade to latest version 2023-12-19 11:55:30 +00:00
recipes-qt qtgrpc: workaround kirkstone build 2024-10-29 14:04:39 +00:00
scripts Conversion script to use new module names 2023-08-28 09:43:23 +00:00
COPYING.MIT initial commit 2020-01-24 11:54:52 +02:00
README.md readme: update Yocto support table 2024-04-15 16:19:02 +03:00

Qt6 OpenEmbedded/Yocto Project layer

This layer depends on:

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

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 minor stabilization branches, 6.x.y for the release branches and lts-6.x.y for commercial LTS releases.

Each Qt release is tagged either as v6.x.y or v6.x.y-lts

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

Yocto \ Qt dev 6.7 6.6 6.5 6.4 6.3 6.2
styhead x x
scarthgap x x x x
nanbield x x x x
mickledore c c c c c
langdale c c c c c
kirkstone x x x x c c x
honister c c c c c
hardknott c c c c c
gatesgarth c c c c c
dunfell x x c c x
dev stable stable LTS EOL EOL LTS

Detailed status of supported Qt versions can be found from https://doc.qt.io/qt-6/supported-platforms.html#supported-qt-versions

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.

QtMultimedia

Qt Multimedia now prefers FFmpeg as the multimedia backend instead of GStreamer. FFmpeg recipe, however, is flagged with LICENSE_FLAGS = "commercial", which means that user must accept the license before FFmpeg can be used in the build. If user accepts the license using LICENSE_FLAGS_ACCEPTED = 'commercial_ffmpeg', the FFmpeg support is enabled in Qt Multimedia. If user doesn't accept the license, Qt Multimedia only uses GStreamer.

Contributing

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

More information about Qt Gerrit and how to use it:

Report bugs on Qt Bug Tracker using Yocto: meta-qt6 layer component.

Layer maintainers