cja
A CMake-compatible build system that generates Ninja build files.
Build a project with a CMakeLists.txt using:
cja
ninja
This is equivalent to the following with CMake:
cmake -Bbuild -GNinja -DCMAKE_BUILD_TYPE=Debug \
-DCMAKE_COLOR_DIAGNOSTICS=1 -DCMAKE_EXPORT_COMPILE_COMMANDS=1
ninja -Cbuild
Install
pip install cja
Or, if you're in a managed Python environment:
pipx install cja
Comparison to CMake
- The
build.ninjafile is generated in your project root, not in the build directory. To allow multiple build configurations in parallel, the file name is<builddir>.ninja. - Paths are relative to the project root, while CMake uses absolute paths. This is faster, reduces output, and also reduces binary size as paths (e.g. for debug symbols) are shorter. When reading output from a Docker container, this lets you click paths and open the correct files in your local editor.
- Instead of a separate tool like CTest, cja generates a phony
testtarget that runs all tests as part of the Ninja build graph, so tests can start as soon as the first test binary is ready. - Colors for compiler diagnostics are enabled by default.
_builddir_/compile_commands.jsonis always generated.- More colorful, simplified output. For example, when downloading dependencies, cja shows progress bars using
Rich, while CMake shows no output (or simple multi-line output when
-DFETCHCONTENT_QUIET=0is specified).
Limitations to keep cja simple:
- Only generates Ninja build files.
- Out-of-tree builds aren't allowed.
- Only supports Linux, macOS, and Windows.
- Only supports clang with a GNU-like command line on Windows.
Build Subcommand
cja supports a build subcommand, which runs ninja automatically afterward.
cja --release / cja build --release
cja --release is equivalent to:
cja -Bbuild-release -DCMAKE_BUILD_TYPE=Release
cja build --release additionally runs ninja:
cja -Bbuild-release -DCMAKE_BUILD_TYPE=Release
ninja -f build-release.ninja
Run Subcommand
cja also generates a run phony target that executes the first executable (or the one set via
VS_STARTUP_PROJECT) in your CMakeLists.txt.
1 maintainer
Metadata
1 maintainer
Release files for cja 0.7.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| cja-0.7.5.tar.gz | 125.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cja-0.7.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 260.1 kB
Release files / cja-0.7.5.tar.gz
| Download URL | cja-0.7.5.tar.gz |
|---|---|
| Size | 125.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63cb5e6019d45c678d38b023227f637108b86445835b12eeeac31f67fb5f297b
|
|
BLAKE2b-256 checksum How to use checksums |
c392e4fca419b80ebb44b5fab73ec8d91186ab756908f9b67049166291f42139
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency logRelease files / cja-0.7.5-py3-none-any.whl
| Download URL | cja-0.7.5-py3-none-any.whl |
|---|---|
| Size | 134.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dbfce032289345d3b18485d61b23069af397e5244b6e80658ac092a3ce307c92
|
|
BLAKE2b-256 checksum How to use checksums |
6544ec8e8d5e6793551d452f76dee2d6deae2541f083907f734b25e31a707f8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.
Transparency log
