Originally posted by cen1
View Post
Despite requests for sub-project support for years in CMake, the team just doesn't care to explicitly support it, leading to half-baked solutions like DownloadProject or ExternalProject. Meson tried to solve this from the get-go with their subproject command which actually feels practical (though it still has some limitations and of course still requires a meson script for the sub-project).
Meson is also closer to autotools as far as the API is concerned which the people from X.org and gang are probably far more familiar with. It does lack a lot of the maturity cruft of autotools has though but that's probably mostly intentional.
I'll also note that people seem to think that Meson uses python as its scripting language. Not the case... it uses a weird subset that looks somewhat like python but lacks anywhere near the full power of python. For instance, you can't define your own functions in the Meson scripting language and templated strings aren't available. I will say that coming from CMake, virtually any language is a welcome sight but it is a little odd.
EDIT: From a practical point of view, meson is very usable. It can do anything CMake can do right now and then some. I don't know if not using cmake is a mistake but using meson probably isn't a mistake.
Comment