@CoBo said in QtCreator constantly "forgetting" CMake property settings:
QtCreator is for me the tool of choice for C++ programming, and CMake is the build tool that I at least prefer over qmake because it is much more powerful - plus the base of all my projects is done with cmake anyway.
Count me as another user with pretty much same use case.
A very common flow: configure CMake project with cmake-gui or even cmake directly -> build it with command-line -> repeat multiple times with multiple projects -> sometime open one of the projects with Qt Creator to write more code/debug/etc.
I remember Qt Creator was able to open an existing cmake build folder (with existing CMakeCache.txt) just fine for a while, and I was happy with it, even though I couldn't preset cmake variables from Qt Creator before running the cmake for the first time for a brand-new build configuration (still cannot, and yes, that is a big deal for my project(s)).
Last few versions (4.12.1, 4.12.2 for sure) this became broken again. If I open an existing cmake build folder (by importing a build configuration or by selecting an existing build folder for an existing QtCreator build configuration) - Qt Creator would delete CMakeCache.txt and re-run cmake from scratch, which actually breaks my build configuration completely(
BTW: my cmake version is 3.16 so it does support filesystem API.