3 ms·
A bunch of tools I work with have recently adopted Meson - things like qemu and libvirt. It's obviously better than autotools, but almost anything is. It also
by rwmj 5y ago
A bunch of tools I work with have recently adopted Meson - things like qemu and libvirt. It's obviously better than autotools, but almost anything is. It also generates Ninja files which makes very parallel builds by default, which is great. Some downsides: I really don't like the configuration. I think using a (sort of) general purpose imperative language was probably a mistake. (Either go all-Python, or do something declarative). I also really dislike out of tree builds and wish it just let you do an in-tree build. So for me it's a mix of good and bad, with the parallel performance being the best thing.
- bonzini 5y agoI like to see a complex build system as a data flow setup where the configuration is the input and the build artifacts are the output. Meson supports that model nicely, and it hides (mostly) what happens at configuration time from what happens at build time. Future versions of Meson could move bits from Meson-time to ninja-time transparently. This, plus the fact that there is no aliasing (objects are either immutable or copied on assignment), means the imperative nature is mostly hidden. Heavily macroized Makefiles can have much more of an imperative style than meson.build files.
- Arnavion 5y agoYou can do an in-tree build just fine? Nothing prevents you from putting the build directory inside the source tree itself.