Details
-
Bug
-
Resolution: Out of scope
-
Not Evaluated
-
None
-
Qt Creator 4.3.1
Description
I use a custom script that sets up a CMake build tree for me. This is automated and does not need a long document. With QtCreator, I need that long document again to explain all entries of a toolchain file so that they can fill in a dummy "Kit"!
In QtCreator, I try to setup a "Kit" and fill in all tools so that QtCreator is happy and I can use QtCreator as debug frontend. That step is already wrong because QtCreator assumes that I want it to be the master interface to my project. Why does every IDE do this wrong?
When changing ANYTHING in the Kit, even just the deploy target device(!!!), then QtCreator tries to reconfigure and regenerate the build tree. How can I stop that? That absolutely makes no sense for me!
It generates output like
Running "C:\Program Files\CMake\bin\cmake.exe -E server "--pipe=\\.\pipe\{9bfd0dc3-880c-40bd-bcb0-2a7efe393c64}" --experimental" in c:\path\to\my\build\tree. Configuring done Generating done
The last two lines should no be there. The Build tree is already configured and generated, there is absolutely no need to do that again.
Actually, I want QtCreator to work the other way round:
- Allow to use a build directory as project and deduce the entries for a "Kit" from it (all information is there). Yes, multiple configurations may not be possible in this case.
- Allow a custom script to run for the configuration and generation step instead of enforcing to run cmake itself with most-likely insufficient information.
- Add support for specifying path to make tools like Ninja in "Kit" (yes, I do NOT have the ninja tool in PATH).