I'm wondering whether that will result in expending a lot of effort to move from a poorly-supported build system to a different poorly-supported build system.
I’m not sure whether the former is autoconf/make or cmake, but count me as another vote for cmake over meson. CMake has direct support from Microsoft (Visual Studio 2017 can auto-ingest CMake-based files as soon as they’re checked out) and JetBrains CLion and is in use by LLVM, KDE, Qt, Blender, libpng, cURL, LAPACK, MySQL/MariaDB, OpenCV, SDL, the Dolphin Gamecube emulator etc.
So the tooling around people using it is there and it’s used by some very large and mature projects covering a variety of domains: I don’t know if it’s “poorly supported” (the documentation leaves something to be desired), but if CMake has trouble down the line a
lot of very important projects will be in trouble. It seems like a pretty safe bet given the sheer inertia of the list above.
--
Jason Petersen
Software Engineer | Citus Data
303.736.9255