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.
To install the latest version available, use:
$ xpm install --global @xpack-dev-tools/ninja-build@latest
To install this specific version, use:
$ xpm install --global @firstname.lastname@example.org
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.
- [#1] on Windows, starting npm/xpm applications via the
.cmdforwarders still not fully functional, as it was shown when trying meson; the problem was identified as the missing quotes around the command passed to cmd.exe.
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.
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 library.so | grep runpath 0x000000000000001d (RPATH) Library rpath: [$ORIGIN]
In the GNU ld.so search strategy, the
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
The original documentation is available from:
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:
For the prerequisites and more details on the build procedure, please see the How to build page.
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:
bab7c9f80775d71c28bbf0c7322e9209059ca435276df221506c6a84d501e822 xpack-ninja-build-1.10.2-3-darwin-x64.tar.gz ae093330e3f55f983a8e8de3b3ee4d6962d8ac1ff439fa505ffa34e475d5c5f2 xpack-ninja-build-1.10.2-3-linux-arm64.tar.gz 97baabda3edf74726e5d60682a9b0fe95fdc8895e631694a65974ea94e4650a6 xpack-ninja-build-1.10.2-3-linux-arm.tar.gz 52ed3dd29174b584bd57ea100f69ab5b1888df7064b9368ba8522fb99957cdbd xpack-ninja-build-1.10.2-3-linux-ia32.tar.gz b49522febca4c4605e335b9482b96994f530729337623efc153098738f517e62 xpack-ninja-build-1.10.2-3-linux-x64.tar.gz 223a3a32c00c12f3a64e42994c88d28a2595f70369893187fef2c96deb0c9e5c xpack-ninja-build-1.10.2-3-win32-ia32.zip e25d9f00bb4052eb6c61641f69ea7dcbf8ab45212d3c2078c98ef2cd1a074a5e xpack-ninja-build-1.10.2-3-win32-x64.zip
- GitHub xpack-dev-tools/ninja-build-xpack
- this release
- all xPack releases
- individual file counters (grouped per release)
- npmjs.com @xpack-dev-tools/ninja-build