qtgraphs/.cmake.conf

set(QT_REPO_MODULE_VERSION "6.10.0")
set(QT_REPO_MODULE_PRERELEASE_VERSION_SEGMENT "alpha1")
set(QT_EXTRA_INTERNAL_TARGET_DEFINES "QT_NO_AS_CONST=1")
list(APPEND QT_EXTRA_INTERNAL_TARGET_DEFINES "QT_NO_FOREACH=1")
Bump version to 6.10.0 Change-Id: I97e17ecb19564aaabb1b09855af1c78920a56d70 Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org> 2024-12-10 07:10:52 +00:00			`set(QT_REPO_MODULE_VERSION "6.10.0")`
Initial commit 2023-03-02 13:45:23 +00:00			`set(QT_REPO_MODULE_PRERELEASE_VERSION_SEGMENT "alpha1")`
			`set(QT_EXTRA_INTERNAL_TARGET_DEFINES "QT_NO_AS_CONST=1")`
Mark the module as free of Q_FOREACH, except where it isn't 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-115797 to keep track of this. Task-number: QTBUG-115797 Change-Id: If97ca6e164759a413dce8bcc72ab3d3a3b19b017 Reviewed-by: Tomi Korpipää <tomi.korpipaa@qt.io> Reviewed-by: Sami Varanka <sami.varanka@qt.io> 2023-08-04 12:36:28 +00:00			`list(APPEND QT_EXTRA_INTERNAL_TARGET_DEFINES "QT_NO_FOREACH=1")`