path: root/tests/auto/cmake/mockplugins/mockplugins1
diff options
authorAlexandru Croitor <>2022-08-02 18:39:07 +0200
committerAlexandru Croitor <>2022-08-03 17:14:55 +0200
commit15117f84bb9a5fd191105b2a4d8ebafc6c819fb9 (patch)
tree03b0c257325bd1da4af35a685dc2175d72d14b76 /tests/auto/cmake/mockplugins/mockplugins1
parent97fa1f24b9e35fde280f282648babdf7d2171020 (diff)
CMake: Relax constraint on not having feature values change
Previously if qtbase was built with feature A set to ON, then building qtsvg, then rebuilding qtbase with feature A set to OFF, trying to build qtsvg would fail with an error message at configure time saying that the feature value has changed. This check was added quite early in the Qt CMake port, presumably to catch accidental reconfigures that might cause long rebuilds. This has dubious benefit though. We constantly had people telling us they get the error without knowing what to do. The usual advice was to remove CMakeCache.txt and reconfigure. Instead of forcing people to suffer this dance, relax the constraint by issuing a warning instead of an error, and make it more clear why a rebuild might happen (a changed feature value might change the generated module C++ header file which in turn might be included by various project sources). Amends 20633d97abed0f6025572f87c9359272b4713384 Pick-to: 6.2 6.3 6.4 Fixes: QTBUG-95834 Change-Id: I992bd61024958869f3b995471b4c7ff75e3a33a0 Reviewed-by: Jörg Bornemann <>
Diffstat (limited to 'tests/auto/cmake/mockplugins/mockplugins1')
0 files changed, 0 insertions, 0 deletions