Qt 6.2.7 open source content was missing a few license headers, hence
a new update round. Amends commit 8d160af7dd.
Change-Id: Ie8dfded3e8fdd1d965d4f38b8fc7d926c2c5803f
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
Some components use also base name in NVD CVE database product:
| sqlite> select * from products where product like 'qtbase';
| CVE-2019-18281|qt|qtbase|5.11.0|>=|5.11.3|<=
| CVE-2019-18281|qt|qtbase|5.12.0|>=|5.12.5|<
| sqlite> select * from products where product like 'qtsvg';
| CVE-2021-45930|qt|qtsvg|5.0.0|>=|5.15.2|<=
| CVE-2021-45930|qt|qtsvg|6.0.0|>=|6.2.1|<=
Change-Id: Ic8cbc59522731f49907e10bf08c6a00a213ae006
Reviewed-by: Samuli Piippo <samuli.piippo@qt.io>
(cherry picked from commit d4f4b54f4e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Git clones from google fail frequently with:
>> fatal: early EOF
>> error: index-pack died
Switch to using github mirror for the git-repo repository.
Change-Id: Id0cbf3c59e50869d62880e56251b003490c4c1ee
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit 61f984c49d)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Qt modules recently lost all their release branches in their git
repositories. This broke previous releases since bitbake validates
that SRCREV can be found from the current branch. Add additional
parameter to repo URI to stop bitbake from validating the SRCREV.
Task-number: QTBUG-109319
Change-Id: Ib61164839fdbc5938a23b92ab03f3c07e945812f
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit 28842c8014)
Change the CI dependencies so that we always get the VM configurations
from the qt5.git dev branch. This makes sure that all Yocto builds,
regardless of the Qt version, are using the same host VM version.
Change-Id: Iceb5ca006b8d83ed636d59566a115d64d3919e38
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit a162d8c5a6)
Until the opensource lts releases are pushed to code.qt.io,
we need to override the git configurations to fetch the modules
from the tqtc repos. This add the same configs as qt6-lts.inc did
when the release was commercial-only, but only for the CI builds.
Change-Id: I789b3600c3aa0a33beeff3cf895944fae51de86c
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Opensource releases will be merged to 6.2 branch.
Change-Id: I7704d8d6c476afd500f47a6245d3b3dcba23902e
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
This reverts commit 0523ed869b.
The LTS releases are pushed to opensource, we again need to
use the public repos and branches.
Change-Id: I1835fcd909773e6219fd3040a97c394ffc6ab327
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Change the CI dependencies so that we always get the VM configurations
from the qt5.git dev branch. This makes sure that all Yocto builds,
regardless of the Qt version, are using the same host VM version.
Change-Id: Iceb5ca006b8d83ed636d59566a115d64d3919e38
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit a162d8c5a6)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
QtInsightTracker is a commercial-only module.
Task-number: ANALYTICS-238
Change-Id: I30412dec8552898b76865402c2e2ccfcae8d1904
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
(cherry picked from commit 56710e8724)
Add a global variable that can be used whenever meta-qt6 layer is
included in the build to identify the Qt version.
Change-Id: I3d40d151e0be9f9123d2bf7cbe34a44861e7b093
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
(cherry picked from commit a6f9d2499b)
Qt might be using different path to libs.
Change-Id: Iaf0721af1c5e74cd293437cb35c287bd820fa3a5
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
(cherry picked from commit 91a21476ab)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Keep the SECURITY_CFLAGS set by Yocto builds also in the SKD's
CMake toolchain file. Instead remove only the fortify flags,
since they add unnecessary warnings when doing debug builds
with Qt Creator.
Change-Id: Ia01f92f21c4f68b1be0d57f9a586a34acbe2333c
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
(cherry picked from commit a942032591)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
The qmake mkspec additions are used with the sdk when the toolchain
environment-setup script hasn't been run. Instead of adding those in
the sdk creation phase, do it already in the qtbase recipe.
Change the mkspec also so that CC/CXX has only the compiler executable,
but none of the compile flags that usually are there in Yocto builds.
This keeps Qt Creator happier as well.
Task-number: QTCREATORBUG-27372
Change-Id: If27d595965df59ff9846f4c773469889a8480040
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
(cherry picked from commit cfaf86d808)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
Add support for using qmake directly from Yocto build sysroots
with following workflow:
bitbake meta-ide-support
bitbake build-sysroots
. ./tmp/deploy/images/qemuarm64/environment-setup-cortexa57-poky-linux
qmake & make
Use configurable sysroot paths in populate_qt6_sdk_base so that it can
be reused also for yocto build sysroots.
Fixes: QTBUG-108778
Change-Id: Iee48f75edbc62e5adcca318a9f4cf17b7477f4a0
Reviewed-by: Ari Parkkila <ari.parkkila@qt.io>
(cherry picked from commit 0533b8907e)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
