beskid build

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

AOT-compiles a resolved Beskid program and writes build artifacts. Executable and library outputs link only the matching hash-validated ABI-v5 runtime kit installed with the toolchain; --kind object emits no runtime dependency. Progress output can be animated unless --plain is set.

Project and entrypoint

Argument	Description
[INPUT]	Optional .bd entry
--project	Project directory or Project.proj path
--target	Target name from the manifest
--workspace-member	Workspace member when resolving via Workspace.proj
--frozen	Require lockfile match; forbid updates
--locked	Require an existing lockfile
--entrypoint	Entry function when applicable

Output and linking

Argument	Description
--kind	exe, shared, static, object (defaults follow project target kind)
--release	Release profile (otherwise debug)
--target-triple	LLVM-style triple (e.g. x86_64-unknown-linux-gnu)
--output	Final artifact path (default derived next to input / target stem)
--object-output	Optional explicit object file path

Runtime and exports

Argument	Description
--export	Repeatable: explicit symbols to export in shared/static artifacts
--prefer-static / --prefer-dynamic	Link mode preference (mutually exclusive with each other)

Diagnostics

Argument	Description
--verbose-link	Print linker invocations
--plain	Plain line-based progress (no step bar or dependency graph panel)

Example

beskid build --project path/to/Project.proj --release

← Back to CLI command reference