-
Suggestion
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt Creator 18.0.0
-
None
Steps to reproduce.
1) Configure analogclock on the command line
cd ~/my_analog_build_dir ~/Dev/qt/official/6.9.2/macos/bin/qt-cmake ~/Dev/qt/official/Examples/Qt-6.9.2/widgets/widgets/analogclock
2) Start Creator, and ensure that the Autorun CMake option is disabled in Settings -> CMake -> General -> Autorun CMake.
3) Open the ~/Dev/qt/official/Examples/Qt-6.9.2/widgets/widgets/analogclock/CMakeLists.txt as a project
and import the existing build from ~/my_analog_build_dir
4) Observe that Creator automatically runs cmake in the build dir, because it doesn't see a .cmake subdir with the cmake api response file in the build dir.
This is unexpected, given that Autorun CMake is off.
I understand that Creator doesn't have the necessary information to display the project without the cmake api response file, but the developer should be informed about that and should be allowed to decline running cmake, because that might cause unexpected results.
One case of that is QTCREATORBUG-33489 but there might be more.
As a developer with Autorun CMake is off, i expect to see a dialog explaining the situation, showing me which cmake command it intends to run, and allow me to decline running cmake.
I can then choose to run the cmake api query myself, or let Creator do it, if I deem it safe.
- relates to
-
QTCREATORBUG-33489 Importing a qt cmake project build into Creator creates a Qt Kit with the default Creator cmake version, rather than trying to detect the one that was used for the project before importing
-
- Open
-