On Sun, Jul 22, 2018, 12:58 Иван Комиссаров <[email protected]> wrote:
> But only qmake works fine with new clang model, other build systems pass > incorrect parameters to clang so it can’t compile my files (code model > complains about missing std:: classes/functions, however the code compiles > so project file is correct) > Please file but reports for those cases then. That *should* work and it does work with all my test projects. That’s true, but despite huge CMake community, Qt Creator’s CMake > integration still is not in feature-parity with qmake. > CMake had never been a first class citizen in creator: Noboby inside the Qt company used cmake in earnest, so nobody cared for CMake support -- once we had rudimentary functionality in place. When I spend some month improving CMake support in creator the feedback was fantastic and there was and still is *lots* of it! There are *LOTS* of people using qt creator and CMake out there! But you are right: Some features are not possible with cmake. This includes most operations that involve modifying CMakeLists.txt files directly, including e.g. adding files to a target. One can hack something that will probably work most of the time, but that is as good as it will get. That is the same situation we also have with qbs by the way: Add some JS into the wrong place and toolability is gone... Do stuff sensibly and all is well. Best regards, Tobias
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
