Version 1.10.2-4 is a maintenance release; it is a rebuild with the latest build environment.

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

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


The binary files are available from GitHub releases.


  • Intel GNU/Linux 32/64-bit: any system with GLIBC 2.15 or higher (like Ubuntu 12 or later, Debian 8 or later, RedHat/CentOS 7 later, Fedora 20 or later, etc)
  • Arm GNU/Linux 32/64-bit: any system with GLIBC 2.23 or higher (like Ubuntu 16 or later, Debian 9 or later, RedHat/CentOS 8 or later, Fedora 24 or later, etc)
  • Intel Windows 32/64-bit: Windows 7 with the Universal C Runtime (UCRT), Windows 8, Windows 10
  • Intel macOS 64-bit: 10.13 or later


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 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.10.2-4.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


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 global store:

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


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

The current version is based on:

  • Ninja release 1.10.2 from Nov 28th, 2020.


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


  • 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).


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

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

In the GNU 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.


Similarly, on macOS, the dynamic libraries are adjusted with otool to use a relative path.


The original documentation is available in the share/doc folder.


The binaries for all supported platforms (Windows, macOS and Intel & Arm 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 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:




The SHA-256 hashes for the files are:








Deprecation notices

32-bit support

Support for 32-bit Intel Linux and Intel Windows will most probably be dropped in 2022. Support for 32-bit Arm Linux 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 will most probably be dropped in 2022, and the minimum requirement will be raised to GLIBC 2.27, available starting with Ubuntu 18 and RedHat 8.

Download analytics

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