The CLI uses one Cargo target directory for compatible native builds from different BornEngine projects. By default, it is <user-cache>/BornEngine/cargo-target; Cargo fingerprints still separate engine versions, target triples, Rust toolchains, profiles, and feature sets.
bornengine cache path
CARGO_TARGET_DIR=/mnt/fast-cache bornengine cache pathAbsolute CARGO_TARGET_DIR values are preserved. Relative values are anchored to the project root for native builds and cache warm; cache path uses the same project root when run inside a game project, or the current directory outside one. This keeps the path stable even when Perry runs from its build-output directory. The CLI does not delete or relocate package-local target directories. The first build for a missing version, target, toolchain, or feature combination still compiles its dependencies; later compatible builds reuse cached artifacts.
Warm a project build
After installing a project’s dependencies, cache warm compiles the selected BornEngine native engine/profile directly with Cargo. It does not run Perry, compile the TypeScript entry point, package assets, or launch the game.
bornengine cache warm
bornengine cache warm --release --jobs 4Without --release, the warm operation uses the same fast incremental Cargo development profile as run and dev. --release warms optimized artifacts. Cargo can reuse artifacts only when the project’s engine version, host target, feature set, Rust toolchain, and build profile match.
Job limits
Pass --jobs N to cache warm, build, run, or dev to set CARGO_BUILD_JOBS. The value must be a positive integer. When omitted, an inherited CARGO_BUILD_JOBS value remains in effect; otherwise Cargo chooses its own concurrency. The CLI does not impose a machine-wide job limit.
run and dev use Rust optimization level 1 with incremental compilation by default to shorten iteration time. Add --release to either command for optimized output. build remains optimized. Installing the CLI does not compile engine artifacts because the target project, engine version, and features are not known until a game project is selected.
Command reference
Show the native build cache path
Display the active shared Cargo target directory.
bornengine cache pathOptions
CARGO_TARGET_DIR selects a custom target directory-v, --verbose (repeatable)
Behavior
Uses the per-user BornEngine cache directory unless CARGO_TARGET_DIR is already set. It works outside a project.
Examples
bornengine cache pathCARGO_TARGET_DIR=/mnt/fast-cache bornengine cache pathWarm the native engine cache
Build the project's selected engine and native features without compiling its TypeScript entry point.
bornengine cache warm [--release] [--jobs <n>]Options
--release selects optimized Cargo output--jobs <n> sets a positive Cargo job limit-v, --verbose (repeatable)
Behavior
Requires installed project dependencies and a supported native host. Uses the same target directory and feature profile as native project builds; it does not run Perry or launch the game.
Examples
bornengine cache warmbornengine cache warm --release --jobs 4