Logo since 2019 | |
Meson configuring dav1d | |
Developer(s) | Jussi Pakkanen |
---|---|
Initial release | 2 March 2013 |
Written in | Python |
Operating system | Cross-platform |
Type | Software development tools |
License | Apache License 2.0 |
Meson (/ˈmɛ.sɒn/)[1] is a software tool for automating the building (compiling) of software. The overall goal for Meson is to promote programmer productivity.[2] Meson is free and open-source software written in Python, under the Apache License 2.0.[3]
Being written in Python, Meson runs on Unix-like operating systems, including macOS, as well as Microsoft Windows and on other operating systems.
Meson supports the C, C++, CUDA, D, Objective-C, Fortran, Java, C#, Rust, and Vala languages,[4] and has a mechanism for handling dependencies called Wrap.
Meson supports GNU Compiler Collection, Clang, Microsoft Visual C++ and other compilers, including non-traditional compilers such as Emscripten and Cython.[5] The project uses ninja as the primary backend buildsystem, but can also use Microsoft Visual Studio or Xcode backends.
The syntax of Meson's build description files (the Meson language) borrows from Python, but is not Python: It is designed such that it can be reimplemented in any other language;[6] for example, muon[7] is a C implementation and Meson++[8] is a C++ implementation – the dependency on Python is an implementation detail.
The Meson language is intentionally not Turing complete, and can therefore not express an arbitrary program.[6] Instead, arbitrary build steps beyond compiling supported languages can be represented as custom targets.
The Meson language is strongly typed, such that builtin types like library, executable, string, and lists thereof, are non-interchangeable.[9] In particular, unlike Make, the list type does not split strings on whitespace.[6] Thus, whitespace and other characters in filenames and program arguments are handled cleanly.
Meson | CMake | Make | |
---|---|---|---|
Datatypes | Yes | No | No |
List datatype | Yes | semicolon delimited string | whitespace delimited string |
Dictionary datatype | since 0.47.0 | No | No |
File globbing | No | Yes | Yes |
Extensible via custom functions | No | Yes | Yes |
Can read output of arbitrary commands (at configure time) | run_command | Yes | Yes |
Can run arbitrary commands at build time as recipes of custom targets | Yes | Yes | Yes |
As with any typical buildsystem, correct incremental builds is the most significant speed feature (because all incremental progress is discarded whenever the user is forced to do a clean build).
Unlike bare Make, the separate configure step ensures that changes to arguments, environment variables and command output are not partially applied in subsequent builds, which would lead to a stale build.
Like Ninja, Meson does not support globbing of source files.[6] By requiring all source files to be listed in the build definition files, the build definition file timestamps are sufficient to determine if the set of source files has changed, thereby ensuring that removed source files are detected. CMake supports globbing, but recommends against it for the same reason.[10]
Meson uses ccache automatically if installed. It also detects changes to symbol tables of shared libraries to skip relinking executables against the library when there are no ABI changes. Precompiled headers are supported, but requires configuration. Debug builds are without optimization by default.
speed feature | Meson | CMake | Make |
---|---|---|---|
Prohibits stale builds (partial rebuild against input change) | Yes (unless there are bugs) | If not globbing source files | Recursive Make (an idiomatic pattern) is broken in this respect[11] |
The target that runs tests depends on the tests being built (e.g. test depends on all ) |
Yes | No, and add_dependencies(test all) is forbidden, because the test target is reserved.[12] |
Trivial to add |
Ccache | Automatic | Trivial to add | Trivial to add |
Distcc | Trivial to add | Trivial to add | Trivial to add |
Symbol table aware relinking | Yes | Do it yourself | Do it yourself |
Precompiled headers | Optional | CMake ≥ 3.16[13][1] | Do it yourself |
A stated goal of Meson is to facilitate modern development practices. As such, Meson knows how to do unity builds, build with test coverage, link time optimization etc without the programmer having to write support for this.
Meson | CMake | Autotools | |
---|---|---|---|
Generate a configure script |
No | No | make dist
|
Set correct library installation directory on x86_64 Unix | Automatic | Not standardized | ./configure --libdir=/usr/lib64
|
Meson can automatically find and use external dependencies via pkg-config, CMake, and project-specific lookups,[14] but this only finds installed dependencies, which Meson can not do anything about. Alternatively, or as a fallback, a dependency can be provided as a subproject – a Meson project within another, either contained or as a download link, possibly with patches.[15] This lets Meson resolve dependency hell for the convenience of casual users who want to compile the project, but may contribute to software bloat if a common installed dependency could have been used instead. The mode favored by Linux packagers is therefore fallback.[16]
Meson supports Meson and CMake subprojects. A Meson build file may also refer to the WrapDB service.[15]
use case | Meson | CMake | Cargo |
---|---|---|---|
Finding installed dependencies | pkg-config, CMake packages | CMake module, pkg-config | ? |
Downloading dependencies automatically | subproject | FetchContent[17] | Cargo dependency |
Finding installed dependencies, with download fallback | pkg-config + subproject | CMake module/pkg-config + FetchContent |
? |
pkg-config file generator | Yes | No | No |
Facilitate use as an auto-downloadable dependency | Can be used as a Meson subproject | No | With registration to crates |
Cross compilation requires extra configuration, which Meson supports in the form of a separate cross file, which can be external to the Meson project.[18]
GNOME has made it a goal to port its projects to Meson.[19] As of late 2017, GNOME Shell itself exclusively requires Meson after abandoning Autotools,[20] and central components like GTK+, Clutter-GTK, GLib and GStreamer can be built with Meson.[19]
Many freedesktop.org projects have switched to Meson. Systemd relies on Meson since dropping Autotools in version 234,[21] and also X.Org[22] and Mesa[23] were ported to Meson.
Meson's support for Fortran and Cython was improved to help various scientific projects in their switch from setuptools to Meson, for example SciPy.[24] Meson can also be used as a PEP517 backend to build Python wheels, via the meson-python package.[25]
Other notable projects using Meson include QEMU and PostgreSQL; the Meson homepage lists further projects using Meson.[26]