The xPack Ninja Build
A standalone cross-platform (Windows/macOS/Linux) Ninja Build binary distribution, intended for reproducible builds.
In addition to the the binary archives and the package meta data, this project also includes the build scripts.
This distribution follows the official Ninja build system.
The binaries can be installed automatically as binary xPacks or manually as portable archives.
This distribution is generally one minor release behind the upstream releases. In practical terms, when the minor release number changes, it awaits a few more weeks to get the latest patch release.
This section is intended as a shortcut for those who plan to use the Ninja Build binaries. For full details please read the xPack Ninja Build pages.
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
This command will:
- install the latest available version, into the central xPacks store, if not already there
- add symbolic links to the central store
.cmdforwarders on Windows) into the local
The central xPacks store is a platform dependent
folder; check the output of the
xpm command for the actual
folder used on your platform).
This location is configurable via the environment variable
XPACKS_STORE_FOLDER; for more details please check the
xpm folders page.
It is also possible to install Ninja Build globally, in the user home folder:
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
For all platforms, the xPack Ninja Build binaries are released as portable archives that can be installed in any location.
The archives can be downloaded from the GitHub Releases page.
For more details please read the Install page.
The version strings used by the Ninja project are three number strings
1.11.1; to this string the xPack distribution adds a four number,
but since semver allows only three numbers, all additional ones can
be added only as pre-release strings, separated by a dash,
1.11.1-1. When published as a npm package, the version gets
a fifth number, like
Since adherence of third party packages to semver is not guaranteed,
it is recommended to use semver expressions like
with caution, and prefer exact matches, like
The quick answer is to use the GitHub Discussions.
For more details please read the Support page.
The binary distributions include several open-source components; the
corresponding licenses are available in the installed
- latest xPack release
- all xPack releases
- individual file counters (grouped per release)