Version 1.0.2-1 is a new release; it follows the upstream release.

The xPack Meson Build is a standalone cross-platform binary distribution of Meson Build.

There are separate binaries for Windows (x64), macOS (x64, arm64) and GNU/Linux (x64, arm64 and arm).

Download

The binary files are available from GitHub Releases.

Prerequisites

  • x64 GNU/Linux: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 or later, Fedora 29 or later, etc)
  • arm64/arm GNU/Linux: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 or later, Fedora 29 or later, etc)
  • x64 Windows: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • x64 macOS: 10.13 or later
  • arm64 macOS: 11.6 or later

Install

The full details of installing the xPack Meson Build on various platforms are presented in the separate Install page.

Easy install

The easiest way to install Meson Build is with xpm by using the binary xPack, available as @xpack-dev-tools/meson-build from the npmjs.com registry.

With the xpm tool available, installing the latest version of the package and adding it as a development dependency for a project is quite easy:

cd my-project
xpm init # Add a package.json if not already present

xpm install @xpack-dev-tools/meson-build@latest --verbose

ls -l xpacks/.bin

To install this specific version, use:

xpm install @xpack-dev-tools/meson-build@1.0.2-1.1 --verbose

It is also possible to install Meson Build globally, in the user home folder, but this requires xPack aware tools to automatically identify them and manage paths.

xpm install --global @xpack-dev-tools/meson-build@latest --verbose

Uninstall

To remove the links created by xpm in the current project:

cd my-project

xpm uninstall @xpack-dev-tools/meson-build

To completely remove the package from the central xPack store:

xpm uninstall --global @xpack-dev-tools/meson-build

Compliance

The xPack Meson Build generally follows the official Meson Build releases.

The current version is based on:

  • Meson Build release 1.0.2 from Apr 21, 2023.

Changes

Compared to the upstream version, there are no functional changes.

Bug fixes

  • none

Enhancements

  • none

Known problems

  • none

Embedded Python

To simplify dependency management, this release embeds a Python 3.11.4 instance.

The meson executable is a standard ELF/EXE which includes the Python run-time; the main() function prepares the Python environment and then invokes the Meson main:

  PyRun_SimpleString("from mesonbuild import mesonmain\n");
  PyRun_SimpleString("sys.exit(mesonmain.main())\n");

The Python library is located in the standard location:

  • lib/python3.11
  • lib/python3.11/lib-dynload (the platform dependent files)

The Meson files are located in:

  • lib/python3.11/mesonbuild

To speed up execution, all Python files are compiled and are available only as .pyc.

Shared libraries

On all platforms the packages are standalone, and expect only the standard runtime to be present on the host.

All dependencies that are build as shared libraries are copied locally in the libexec folder (or in the same folder as the executable for Windows).

DT_RPATH and LD_LIBRARY_PATH

On GNU/Linux the binaries are adjusted to use a relative path:

$ readelf -d library.so | grep runpath
 0x000000000000001d (RPATH)            Library rpath: [$ORIGIN]

In the GNU ld.so search strategy, the DT_RPATH has the highest priority, higher than LD_LIBRARY_PATH, so if this later one is set in the environment, it should not interfere with the xPack binaries.

Please note that previous versions, up to mid-2020, used DT_RUNPATH, which has a priority lower than LD_LIBRARY_PATH, and does not tolerate setting it in the environment.

@rpath and @loader_path

Similarly, on macOS, the binaries are adjusted with install_name_tool to use a relative path.

Documentation

The original documentation is available from:

Build

The binaries for all supported platforms (Windows, macOS and GNU/Linux) were built using the xPack Build Box (XBB), a set of build environments based on slightly older distributions, that should be compatible with most recent systems.

For the prerequisites and more details on the build procedure, please see the How to build page.

CI tests

Before publishing, a set of simple tests were performed on an exhaustive set of platforms. The results are available from:

Checksums

The SHA-256 hashes for the files are:

65fbcae443bfb35ee1836aaacb35fc18cf6a5f91ab121d0df0706ae22cc3e3a8
xpack-meson-build-1.0.2-1-darwin-arm64.tar.gz

f53eed8464941e55514062d43d38e1b45131a2ac49e183cd17ed449bf490041c
xpack-meson-build-1.0.2-1-darwin-x64.tar.gz

a848498a2d19170a748b0f7952e94225ad3b0f7e06f11cb5276152625d4f8210
xpack-meson-build-1.0.2-1-linux-arm.tar.gz

dd98bd8127a3ee8b67762ffa88278202f31d73e58046465799fa70471ca5f9c8
xpack-meson-build-1.0.2-1-linux-arm64.tar.gz

fa8dc1f1adb8d5a868b02848ec72c42872bb4985128deb38cf448889c0ecdb74
xpack-meson-build-1.0.2-1-linux-x64.tar.gz

180fe63753745fd7b0b88e815313092c6a265f9075ce5ab52c915ff2c29806cd
xpack-meson-build-1.0.2-1-win32-x64.zip

Deprecation notices

32-bit support

Support for 32-bit x86 GNU/Linux and x86 Windows was dropped in 2022. Support for 32-bit Arm GNU/Linux (armv7l) will be preserved for a while, due to the large user base of 32-bit Raspberry Pi systems.

GNU/Linux minimum requirements

Support for RedHat 7 was dropped in 2022 and the minimum requirement was raised to GLIBC 2.27, available starting with Ubuntu 18, Debian 10 and RedHat 8.

Pre-deprecation notice for Ubuntu 18.04

Ubuntu 18.04 LTS Bionic Beaver reached the end of the standard five-year maintenance window for Long-Term Support (LTS) release on 31 May 2023.

As a courtesy, the xPack GNU/Linux releases will continue to be based on Ubuntu 18.04 for another year.

From 2025 onwards, the GNU/Linux binaries will be built on Debian 10, (GLIBC 2.28), and are also expected to run on RedHat 8.

Users are urged to update their build and test infrastructure to ensure a smooth transition to the next xPack releases.

Download analytics

Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.