3 ms·
Yes it is. CMake was adopted long before it supported everything it supports today.
by jchw 7y ago
Yes it is. CMake was adopted long before it supported everything it supports today.
- pjmlp 7y agoLet us know when Meson gets first class support on Eclipse CDT, Clion, Qt Creator, KDevelop, Android Studio, VSCode and Visual Studio.
- jchw 7y agoOK, ping me in 3 years.
- pjmlp 7y agoSurely. I have seen too many carriages drive by.
- jchw 7y agoActually, there’s already an excellent Meson plugin for VSCode, and a pretty good one for Qt Creator, so I hope you’re a fan of losing bets :p
- pjmlp 7y agoSo far, everyone that has bet against CMake has lost to overtake it. Scons, qmake, waf, premake, Gradle C++, MSBuild, ... I know which horse to bet on.
- jchw 7y agoScons and qmake both predate CMake. It’s weird to characterize them as trying to “overtake” CMake; that’s not really a thing I think happened. As a matter of fact, there was a time when qmake was a better option; it was a fairly complete Makefile generator that had good support for subprojects and out of tree builds. Then again, this is all irrelevant. What these projects all had to offer at one point is historical. Qt has to leave qmake because of qmake. During that time they evaluated many options, including a fairly innovative design called qbs - Qt Build System. In the end, the choice of CMake makes a lot of sense, as it is clearly the best available choice that had ecosystem support. Qt is unlikely to switch build systems again soon. This entire argument has happened before, but instead of meson vs CMake it was CMake vs autoconf. The thing is, I suspect CMake will still exist even as Meson inevitably continues to gain traction, just as autoconf (unfortunately) exists today. There is, in fact, room for more C++ build systems, and almost definitely room for better interop. (Meson and CMake have some interop today.)