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 @email@example.com
The xPack Ninja Build is based on the official Ninja, without any changes.
The current version is based on:
- Ninja release 1.10.1 from Aug 18th, 2020.
Compared to the upstream version, there are no changes.
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:
7d75d2f20f8be2b61953fed26566b627517717831e700c22e0fbd23200a6ab45 xpack-ninja-build-1.10.1-1-darwin-x64.tar.gz 48ba6a6212c3d28eb08076f1946818a9067c523793b1db6c885904caa425dce4 xpack-ninja-build-1.10.1-1-linux-arm64.tar.gz 38df303e3f4c13ba58eaf5229fe0587eda9078a792f7063d7b60eec60f88b276 xpack-ninja-build-1.10.1-1-linux-arm.tar.gz b170cf10ee12608d68d204f2ca8f77d423a0b095ee0d475db835c03829e08c38 xpack-ninja-build-1.10.1-1-linux-x32.tar.gz 7e8683b1e743cf7cae58f85ef500acea0f464a053ac3d4991383fdcefa550c29 xpack-ninja-build-1.10.1-1-linux-x64.tar.gz 6109815a8ed9b8423847fc368ea927b16b55bc3875135fbe642cf9ced0ed60d5 xpack-ninja-build-1.10.1-1-win32-x32.zip 160c3b3ec67d9f821871e947c8eb882ea5cf99e25a08ad03ebdfef2e04830e63 xpack-ninja-build-1.10.1-1-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