AOT build

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

AOT emits native objects you can link and ship—required for type: Mod packages the host loads at compile time.

Crate

beskid_aot::build consumes CodegenArtifact like JIT, then drives platform link steps per Backends JIT/AOT.

Mod artifacts

Mods are not interpreted Beskid scripts in the compiler process. The host loads AOT-compiled mod assemblies per target triple and cache key:

• AOT artifact contract
• Mod AOT-only registration ADR

accTitle: Compiler Mod AOT artifact
accDescr: Beskid Mod source is AOT-built into an object and descriptor that the analysis host loads.
flowchart TB
  modSrc[Mod Beskid sources]
  aot[beskid_aot build mod]
  artifact[mod.descriptor.json + native object]
  host[mod.load in beskid_analysis]
  modSrc --> aot --> artifact --> host

Text equivalent: The AOT builder compiles Mod source into a native object and mod.descriptor.json. The analysis host loads this validated artifact.

CLI

beskid build selects targets and backends per manifest—see build command reference.

Next

CLIF and debug