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

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

There are separate binaries for Windows (Intel 64-bit), macOS (Intel 64-bit, Apple Silicon 64-bit) and GNU/Linux (Intel 64-bit, Arm 32/64-bit).

Download

The binary files are available from GitHub Releases.

Prerequisites

  • GNU/Linux Intel 64-bit: any system with GLIBC 2.27 or higher (like Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • GNU/Linux Arm 32/64-bit: any system with GLIBC 2.27 or higher (like Raspberry Pi OS, Ubuntu 18 or later, Debian 10 or later, RedHat 8 later, Fedora 29 or later, etc)
  • Intel Windows 64-bit: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • Intel macOS 64-bit: 10.13 or later
  • Apple Silicon macOS 64-bit: 11.6 or later

Install

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

Easy install

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

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

cd my-project
xpm init # Only at first use.

xpm install @xpack-dev-tools/ninja-build@latest

ls -l xpacks/.bin

To install this specific version, use:

xpm install @xpack-dev-tools/ninja-build@1.11.1-1.1

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/ninja-build@latest --verbose

Uninstall

To remove the links from the current project:

cd my-project

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

To completely remove the package from the central xPacks store:

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

Compliance

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

The current version is based on:

  • Ninja Build version 1.11.1 from 1.11.1.

Changes

Compared to the upstream version, the Windows version also supports spawning scripts via cmd.exe /c. These scripts are used by npm/xpm to redirect invocations to the central packages repository.

Bug fixes

  • none

Enhancements

  • none

Known problems

  • none

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 online.

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.

The scripts used to build this distribution are in:

  • distro-info/scripts

For the prerequisites and more details on the build procedure, please see the README-MAINTAINER page.

CI tests

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

Tests

TBD

Checksums

The SHA-256 hashes for the files are:

347f01fe91f181bef77fed4b4465af8fca08817ae320bfec202a3980f48d48c3
xpack-ninja-build-1.11.1-1-darwin-arm64.tar.gz

d8192cc82eee37c58697a0e749c47be995bebe0d88f40f619db282fb39833d93
xpack-ninja-build-1.11.1-1-darwin-x64.tar.gz

d6c24a1f0f753064344ad252bbb58ee79a4f36fed9b29ad33ac1f8231eaa893f
xpack-ninja-build-1.11.1-1-linux-arm.tar.gz

0ec0e91d35202784131e9bce8d304ec99e611882f94d42a976d1054ed04be4a5
xpack-ninja-build-1.11.1-1-linux-arm64.tar.gz

ad0576c0741eb1226451b1958ae8ad438731ec51a356a39613c1d31d48a836b4
xpack-ninja-build-1.11.1-1-linux-x64.tar.gz

ff70b47e1e8a8b4fff22b48e0fd3e23ac15c76838b8f4b0db2805dc402f53c43
xpack-ninja-build-1.11.1-1-win32-x64.zip

Deprecation notices

32-bit support

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

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.

Download analytics

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