| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I3bc3feb3657b4309a8667ed5c3af942c3ca343a4
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
By adding it to the default build flags via .cmake.conf.
This amends commit 69404b3f0d4e650c0b21ed07862be49b51c99300.
Task-number: QTBUG-116296
Change-Id: I8e80246dc2283b369f31971aaceeb907b0cfdfd0
Reviewed-by: Tomi Korpipää <tomi.korpipaa@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The density of Q_FOREACH uses is high here, too high for this author,
unfamiliar with this module, to tackle in a short amount of time. But
they're concentrated in just a few TUs, so pick a different strategy:
Mark the whole module with QT_NO_FOREACH, to prevent new uses from
creeping in, and whitelist the affected TUs by #undef'ing
QT_NO_FOREACH locally, at the top of each file. For TUs that are part
of a larger executable, this requires these files to be compiled
separately, so add them to NO_PCH_SOURCES (which implies
NO_UNITY_BUILD_SOURCES, too). Created QTBUG-115807 to keep track of
this.
Ported one that was trivial and where whitelisting of the file with a
single Q_FOREACH would have been more work than directly fixing it.
Task-number: QTBUG-115807
Change-Id: I2fa6c740e35039baf34115af7d69d6c420e4de10
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Tomi Korpipää <tomi.korpipaa@qt.io>
|
|
|
|
|
| |
Change-Id: Ic05861922f864911a87f45f1174f1515bb550d48
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
|
|
|
|
|
|
|
|
| |
Option has not effect anymore.
Pick-to: 6.5
Change-Id: Ic0ff913ae44ac76e7dbac0de9a00823ad171c3c0
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
|
|
|
|
| |
Change-Id: Ia5375cf7baee7f21bc3609b964dd95726b33e792
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
|
|
|
|
|
| |
Change-Id: I6e9c6113662f6509dc9cadc7c8859544b99d1b98
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
|
|
|
|
|
|
| |
Change-Id: If094fc01810b1408e878a977fc95e6283435b77b
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: I1b6ad924e84448771df9046707b40ca80d5361c4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
|
| |
Change-Id: Idcda692a7bd59710d09776faf46ef6bdef4fafb4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
|
|
|
| |
Change-Id: I772665107eee5dd3e2b7f1486250e4b577dacd0f
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The qt-conan-common package implements a base class for Qt leaf
module recipes. The build steps in leaf modules are mostly identical
so it makes sense to put those in the base class.
Dependencies are read by the base class from the 'dependencies.yaml'
which is the same file the CI system uses.
Inheriting class needs to implement 'get_leaf_module_source_folder()'.
Pick-to: 6.2
Task-number: QTBUG-94902
Change-Id: I7cec8a66bfaae3a75e93b1f31ee33c9defda4fe3
Reviewed-by: Jani Heikkinen <jani.heikkinen@qt.io>
Reviewed-by: Tomi Korpipää <tomi.korpipaa@qt.io>
|
|
|
|
| |
Change-Id: Ib75fef0b3ce2091e0b223208c17c45931a7a1d52
|
|
|
|
|
|
|
| |
Change-Id: Ib7c57e40fe7d5d7723273e282f187fa19dfed11f
Reviewed-by: Akseli Salovaara <akseli.salovaara@qt.io>
(cherry picked from commit 5e41fbf51034fcca7ad4415a4219e2d636cc5485)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
|
|
Task-number: QTBUG-89299
Change-Id: I5becbf39605e566c3d32cb5e210d974df9de27da
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@qt.io>
Reviewed-by: Tomi Korpipää <tomi.korpipaa@qt.io>
|