The CMake project manager can import pre-existing/configured build directories. It will then disable the fields of the wizard that would otherwise allow to specific the install prefix, build type and other, additional cmake arguments.

That is fine, but at least the build type remains set and is given to cmake if that command is executed automatically. That is not necessary in the best case and should not happen in the worst case (when the build is under control of an external configure/build system and the IDE is only used for navigating and editing the source).

It should also be possible to select an environment profile in the importer wizard.

Ensuring that the external configure system generates and maintains a compile_commands.json file will limit automatic invocation of cmake, but apparently not eliminated it completely. There should probably be a control for disabling that feature so that the user can decide is s/he prefers to work with potentially out-of-date project information in the IDE or have an IDE with up-to-date information on a potentially misconfigured project. There could be a visual indication when the project information is supposedly out of date, though.


Reproducible: Always

Steps to Reproduce:
1. prepare a cmake-based project with a pre-configured build directory
2. Import a new project in KDevelop; select the project's CMakeLists.txt file
3. Point the importer wizard to the pre-configured build directory without touching any of the other fields


Actual Results:  
Under certain conditions cmake will be called with at least KDevelop's default CMAKE_BUILD_TYPE passed as an argument

Expected Results:  
If cmake is called at all it in this kind of scenario, should be called without arguments, and with the appropriate environment (if that is not the current environment).