Meson (/ˈmɛ.sɒn/)[2] is a software tool for automating the building (compiling) of software. Meson adopts a convention over configuration approach, promoting standard development tools and practice instead of providing unlimited flexibility to the user.[3] Meson is free and open-source software written in Python, under the Apache License 2.0.[4]
_logo_2019.svg){kind=logo} Logo since 2019 | |
 Meson configuring dav1d | |
| Developer(s) | Jussi Pakkanen |
|---|---|
| Initial release | 2 March 2013 |
| Stable release | 1.6.0[1] 
/ 20 October 2024 |
| Repository | |
| Written in | Python |
| Operating system | Cross-platform |
| Type | Software development tools |
| License | Apache License 2.0 |
| Website | mesonbuild |
Interoperability
editMeson is written in Python and runs on Unix-like operating systems, including macOS, as well as Microsoft Windows and on other operating systems.
Meson supports the languages C, C , C#, CUDA, Objective-C, D, Fortran, Java, Rust, and Vala,[5] and has a mechanism named Wrap to handle dependencies.
Meson supports GNU Compiler Collection, Clang, Microsoft Visual C and other compilers, including non-traditional compilers such as Emscripten and Cython.[6] The project uses ninja as the primary backend buildsystem, but can also use Microsoft Visual Studio or Xcode backends.
Language
editThe 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;[7] for example, muon[8] is a C implementation, and Meson [9] 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.[7] 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.[10] In particular, unlike Make, the list type does not split strings on whitespace.[7] Thus, whitespace and other characters in filenames and program arguments are handled cleanly.
| Feature | 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 | non-standard extension on some variants |
| Extensible via custom functions | No | Yes | No |
| 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 |
Speed and correctness
editAs with any typical buildsystem, correct incremental builds are 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.[7] By requiring all source files to be listed in the build definition files, the build definition file timestamps are sufficient to determine whether 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.[11]
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 require configuration. Debug builds are without optimization by default.
This section needs additional citations for verification. (March 2024) |
This section possibly contains original research. (March 2024) |
| speed feature | Meson | CMake | Make |
|---|---|---|---|
| Prohibits stale builds (partial rebuild against input change) | Yes (unless there are bugs)[contradictory] | If not globbing source files[citation needed] | Recursive Make (an idiomatic pattern) is broken in this respect[12] |
The target that runs tests depends on the tests being built (e.g. test depends on all) |
Yes[citation needed] | No, and add_dependencies(test all) is forbidden, because the test target is reserved.[13] |
Trivial to add[citation needed] |
| Ccache | Automatic[citation needed] | Trivial to add[citation needed] | Trivial to add[citation needed] |
| Distcc | Trivial to add[citation needed] | Trivial to add[citation needed] | Trivial to add[citation needed] |
| Symbol-table-aware relinking | Yes[citation needed] | Do it yourself[citation needed] | Do it yourself[citation needed] |
| Precompiled headers | Optional[citation needed] | CMake ≥ 3.16[14][2] | Do it yourself[citation needed] |
Features
editA 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
|
Subprojects
editMeson can automatically find and use external dependencies via pkg-config, CMake, and project-specific lookups,[15] 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.[16] 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.[17]
Meson supports Meson and CMake subprojects. A Meson build file may also refer to the WrapDB service.[16]
- Comparison of dependency resolution use cases in different build systems
| use case | Meson | CMake | Cargo |
|---|---|---|---|
| Finding installed dependencies | pkg-config, CMake packages | CMake module, pkg-config | ? |
| Downloading dependencies automatically | subproject | FetchContent[18] | 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
editCross compilation requires extra configuration, which Meson supports in the form of a separate cross file, which can be external to the Meson project.[19]
Adopters
editGNOME has made it a goal to port its projects to Meson.[20] As of late 2017, GNOME Shell itself exclusively requires Meson after abandoning Autotools,[21] and central components like GTK , Clutter-GTK, GLib and GStreamer can be built with Meson.[20]
Many freedesktop.org projects have switched to Meson. Systemd relies on Meson since dropping Autotools in version 234,[22] and also X.Org[23] and Mesa[24] 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.[25] Meson can also be used as a PEP517 backend to build Python wheels, via the meson-python package.[26]
Other notable projects using Meson include QEMU and PostgreSQL; the Meson homepage lists further projects using Meson.[27]
See also
edit
References
edit- ^ "Release 1.6.0". 20 October 2024. Retrieved 22 October 2024.
- ^ a b "Making build systems not suck (linux.conf.au video)". YouTube. 16 January 2015.
- ^ "High productivity build system".
Meson aims to optimize programmer productivity by providing simple, out-of-the-box support for modern software development tools and practices, such as unit tests, coverage reports, Valgrind, CCache and the like.
- ^ "mesonbuild/meson: The Meson Build System". GitHub. Retrieved 13 April 2016.
- ^ "Reference manual".
- ^ "Compiler IDs".
- ^ a b c d "Meson Frequently Asked Questions".
- ^ "muon.build". Retrieved 27 January 2023.
- ^ Baker, Dylan (28 May 2021). "dcbaker/meson-plus-plus". GitHub. Retrieved 28 May 2021.
- ^ "Meson Syntax".
- ^ "CMake FILE command".
Note: We do not recommend using GLOB to collect a list of source files from your source tree. If no CMakeLists.txt file changes when a source is added or removed, the generated build system cannot know when to ask CMake to regenerate.
- ^ "Non-recursive Make Considered Harmful" (PDF). Microsoft.
Recursive Make is considered harmful for very good reasons (Miller 1998); it is not possible to accurately track dependencies when the build system is constructed of separate components that invoke each other.
- ^ "Make test does not depend on make all". Kitware issue tracker. 23 June 2016. Retrieved 3 September 2020.
- ^ "CMake support for precompiled headers". Retrieved 13 March 2018.
- ^ "Dependencies with custom lookup functionality — Meson documentation".
- ^ a b "Wrap dependency system manual".
- ^ "Meson and 3rd party dependencies. Only one correct way".
- ^ "FetchContent — CMake 3.15.7 Documentation".
- ^ "Cross compilation".
- ^ a b "GNOME Goal: Port modules to use Meson build system".
- ^ "GNOME 3.26 Beta Debuts: More Meson Porting, Wayland Action".
- ^ "Drop support for autotools". GitHub.
- ^ "Meson Support Has Landed In The X.Org Server".
- ^ "Mesa Developers Move Closer To Dropping Autotools Build System In Favor Of Meson".
- ^ "How to build SciPy with Meson".
- ^ "meson-python package on PyPI".
- ^ "List of projects using Meson".
