Source Install

Get
Centauri Running

Centauri ships as Rust source, not prebuilt binaries. The installer auto-builds the compiler for whatever machine it's run on, so one command — cargo run — installs it on macOS, Linux, or Windows.

Current release: v2.0  ·  Phase 10
🦀 Requires Rust (cargo)
Step by Step

Install from Source

No platform-specific downloads. The same three commands work whether you're on macOS, Linux, or Windows — Rust's #[cfg(...)] gates handle the OS-specific work for you.

1
Install Rust, if you don't have it

Centauri builds itself with cargo. If rustup isn't already on your machine:

macOS / Linux
$ curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

On Windows, grab rustup-init.exe from rust-lang.org and run it — it sets up cargo and the MSVC toolchain for you.

2
Get the source

You need the Centauri/ folder with both Centauri_installer/ and Centauri_compiler/ as siblings — the installer finds the compiler automatically by walking up from wherever it's run.

any OS
# from the unzipped / cloned Centauri/ folder
$ cd Centauri/Centauri_installer
3
Run it

One command. It builds Centauri_compiler in release mode, deploys the binary, and adds it to your PATH — on macOS, Linux, and Windows alike.

any OS
$ cargo run

Restart your terminal (or re-source your shell profile) and Centauri is on your PATH. To remove it later: cargo run -- --uninstall.

Under the Hood

What cargo run Actually Does

No magic — just a small Rust program doing the same four things a human would, automatically, for whichever OS it detects.

01
Finds the compiler workspace
Walks up from the current directory looking for a sibling Centauri_compiler folder with a valid Cargo.toml.
02
Builds the native binary
Runs cargo build --release --bin Centauri inside that workspace, then copies the resulting binary to a per-user local data directory.
03
Handles OS-specific provisioning
Sets the executable bit on macOS/Linux; on macOS it also strips Gatekeeper quarantine flags and applies an ad-hoc codesign.
04
Updates your PATH
On Windows it edits HKEY_CURRENT_USER\Environment via the registry and broadcasts the change. On macOS/Linux it appends an export PATH line to your .zshrc or .bashrc.