Build and install from source

Build and install Oko from source#

Use the existing canonical Oko checkout. Requirements are macOS 14 or newer, a Rust toolchain and Git on PATH.

Pinned Git dependencies#

The repository's .cargo/config.toml sets net.git-fetch-with-cli = true. Cargo therefore uses the Git executable's configured transport and credentials for pinned Git dependencies, both from the checkout root and from rust/. No dependency is copied into the checkout and no local-path replacement is used.

A failed fetch retains the actual Git command, remote and cause. For example, upload-pack: not our ref <revision> means that consumer could not retrieve the requested object from that remote; it is not a compiler error or proof that the object does not exist in a developer's checkout. A successful fetch in a checkout already holding the object does not prove a fresh Cargo consumer can retrieve it. Publish the dependency revision through its normal delivery path before updating a consumer to an API that revision introduces.

Build#

Run from the checkout root:

cargo check --manifest-path rust/Cargo.toml --locked
cargo build --manifest-path rust/Cargo.toml --release --locked

A dependency's required public API must exist at its pinned revision. A compiler error naming a missing variant or symbol remains a failed build; changing the category to a different one or copying the dependency is not a repair. Compilation is not qualification of the CLI, native API, broker or Desktop.

Signed installation#

rust/target/release/oko install

oko install requires stado on PATH and preserves the installed code requirement. --identity NAME selects an exact signing identity; otherwise stado product signing selects it. For non-interactive signing, provide WISENT_CODESIGN_CERTIFICATE_PEM and WISENT_CODESIGN_PRIVATE_KEY_PEM. Missing, ad-hoc or incompatible identities are refused without replacing the destination, as is self-installation. The install command reference covers --into PATH, exact refusals, automatic broker handover and declaration of standing routines.

The installed CLI and Oko Desktop are separate surfaces: installing one does not install or update the other. Continue with sign-in and source adoption. Product qualification requirements are on Release qualification.