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.0 from Jan 28th, 2020.
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 (added in mid-2020)
- 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:
2467085f1d8948857f62fb3db65b4aa6a1da78df215483bef544b9181f8a86b8 xpack-ninja-build-1.10.0-1-darwin-x64.tar.gz 6d1effe9cb8c84c2dbfc51f99573243a08f89ac1bc3873e4a7a9214705de41ee xpack-ninja-build-1.10.0-1-linux-arm64.tar.gz 409ac19823457c3abfd5325035cbe7f8e149198969548706732b3f4374973323 xpack-ninja-build-1.10.0-1-linux-arm.tar.gz 090ee866ce6a0bd24dace2fbd4c8c6ea948d9abbf6c74f79d2f892a7289ab8bf xpack-ninja-build-1.10.0-1-linux-x32.tar.gz ffa1962f2388a283326239b455bdd4543771023c7c458f01b7dbe3b32c9fd54e xpack-ninja-build-1.10.0-1-linux-x64.tar.gz 92d26576285c03e89b44a9925d85704f1d0126ca388dc1a928c702b380de3590 xpack-ninja-build-1.10.0-1-win32-x32.zip b36de95f129376d32da0844f8429f4a02a87202a8179417dcb9c35ca2fd95977 xpack-ninja-build-1.10.0-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