Version 1.10.2-2 is a maintenance release of the xPack Ninja Build package, fixing the spawning of cmd.exe scripts on Windows.

The xPack Ninja Build is the xPack distribution of the Ninja build system.

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.


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.

To install the latest version available, use:

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

To install this specific version, use:

xpm install --global @xpack-dev-tools/ninja-build@1.10.2-2.1


The xPack Ninja Build is based on the official Ninja, without any changes.

The current version is based on:

  • Ninja release 1.10.2 from Nov 28th, 2020.

Bug fixes

  • none


  • none


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 global xPacks store.

Known problems

  • [#1] as discoverd after starting to use meson, starting applications on Windows was still problematic; fixed on 1.10.2-3.

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 same folder as the executable.


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.


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


The original documentation is available from:

Supported platforms

Binaries for Windows, macOS and GNU/Linux are provided.

The binaries 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.

  • Intel GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 12 Docker container
  • Arm GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 16 Docker container
  • Windows: all binaries were built with mingw-w64 GCC 9.3, running in an Ubuntu 12 Docker container
  • macOS: all binaries were built with GCC 9.3, running in a separate folder on macOS 10.10.5.


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.

Travis tests

The first set of tests were performed on Travis, by running a simple script to check if the binaries start on a wide range of platforms and distributions:




The SHA-256 hashes for the files are:








Download analytics

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