Install

Install

Source build only

Cale install currently starts from source builds

Cale does not ship end-user binary releases yet. The current path is to clone the repository and build from source. Future macOS-first GitHub Releases binaries can be added here without changing the page structure.

macOS binary Archive download

Source Release Developer build

Recommended path: source build

This is the most accurate install path today. Build the compiler and check Lacail and Qstar through their Makefile boundaries.

Planned path: GitHub Releases

The first binary path is expected to be macOS, with Linux and Windows artifacts added as the platform story matures.

macOS binary Archive download

Developer path: full checks and subproject checks

This path is for contributors who want to verify the compiler and standalone tools separately.

dev artifact

Platform status

Platform	Status	Notes
macOS	Primary	Source build path today. Planned first binary release target.
Linux	Expanding	Compile/check boundaries first, then broader ELF and platform support.
Windows	Compile stub	COFF and platform diagnostics are expected to grow gradually.

Project status

Project	Boundary	Install/build status
Cale compiler	root Makefile	Source build path through root make and check targets.
Lacail	lacail/Makefile	Standalone debugger project checked through its own Makefile.
Qstar	qstar/Makefile	Separate adjacent tool checked through its own Makefile.

Clone

Copy command

git clone https://github.com/deeyed/cale.git
cd cale

Cale compiler

Copy command

make
make check

Standalone tools

Copy command

make -C lacail check
make -C qstar check

Release-ready shape

• When release binaries exist, the Release tab will add curl commands and archive buttons.
• The source build path remains the fallback for platforms without binary artifacts.
• Lacail and Qstar stay visible as separate tool build states instead of being folded into Cale core.

Links

• Docs
• Getting Started
• Releases