docs.rs failed to build hl-engine-0.1.0
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.

hl-engine

hl-engine is the safe Rust interface to the statically linked C engine. The crate ships one native archive containing both Linux guest backends for each supported AArch64 host:

aarch64-apple-darwin
aarch64-unknown-linux-gnu

The runtime is process-isolated because the two production translators intentionally own independent global JIT state. Guest::Aarch64 and Guest::X86_64 select the child backend without asking applications to choose a Cargo feature. There is no daemon, shell script, GUI, GPU, compositor, or Chrome integration.

use hl_engine::{Config, Engine, Guest, Sandbox};

let engine = Engine::new();
let config = Config::new()
    .root("/var/lib/hl/alpine")
    .working_dir("/work")
    .env("TERM", "xterm-256color")
    .memory_limit(512 * 1024 * 1024)
    .process_limit(256)
    .sandbox(Sandbox::Enabled);
let exit = engine
    .command(Guest::X86_64, "/bin/sh")
    .config(config)
    .args(["-c", "echo hello"])
    .status()?;
assert!(exit.success());
# Ok::<(), Box<dyn std::error::Error>>(())

Command::spawn returns Child for try_wait, wait, output, or force_stop. Dropping a live handle force-stops and reaps its engine process. Command settings are serialized through the C engine's versioned hl_launch_config wire format; ambient HL_* variables are not used.

The published crate contains a pinned static archive for each supported host target. Cargo selects and links the matching archive without compiling C or downloading anything. Child isolation reexecutes the downstream application and activates the native backend before Rust main. macOS applications must be signed with the JIT entitlement. Exact source commit, checksums, and fixture provenance are recorded in assets/PROVENANCE.md.

hl-engine 0.1.0

hl-engine