Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
Qt Creator 14.0.2
-
None
Description
QtCreator runs a fallback scanner if project resolution via CMake fails. I want the option to disable the fallback scanner entirely as it's not useful and it blocks me from quickly re-run CMake with modified settings. Instead, it would be better to simply show the project file tree so that the user has a chance to modify the CMakeUserPreset.json for instance.
Steps to reproduce:
- Create a CMake project folder that contains vcpkg as a submodule. This contains a gazillion files.
- Open the CMake project in QtCreator and ensure that project resolution fails
- QtCreator will run the fallback scanner. That takes minutes.
- Try to abort the fallback scanner. It takes up to 10-20s for the scanner to really abort.
Suggested behavior:
- User opens a CMake project
- Project resolution fails
- QtCreator shows the unfiltered file tree of the project folder
- User may change a CMake user preset or adjust the kit or even another file in the project and is able to immediately re-run CMake
Background:
If I opened a project via a CMake file, it is very likely that I want to explore the project via CMake and only CMake. I don't want any intelligent fallback mechanism as it takes my precious time.