Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
Qt Creator 4.15.0-beta1
-
None
-
637d45c66a1e1eb30db2479a132cbb72bee097a7 (qt-creator/qt-creator/4.15)
Description
There are several ways how to run into this, for example:
- Do a build of your application on the command line, with some CMAKE_BUILD_TYPE
- Open the project in Qt Creator and configure some build configuration(s)
- Change the build directory of some build configuration to the existing build
Expected: The build directory is taken as "the whole truth", Qt Creator successfully parses the project
Actual: If the existing build was done with a different CMAKE_BUILD_TYPE than the implicit build type that was set for the build configuration, for example if you did a RelWithDebInfo build and point the Debug build configuration to that build directory, parsing the project fails with the non-descriptive warning "project was not successfully parsed".
Qt Creator should accept the new build directory as the new truth about the build configuration. If the new build directory has some build type, the build configuration should just have that build type. I realize that for multi-config generators that is not unique - so for multi-config generators the build configuration should have a visible, user-choosable build type property instead of the current hidden one.
Attachments
Issue Links
- relates to
-
QTCREATORBUG-25509 Top-level CMake projects containing no target are not resolved
- Closed
- mentioned in
-
Page Loading...