Build, run, and test

Build and run use ahead-of-time compilation. run creates a temporary executable and starts it. build preserves the requested output.

Prerequisites

Start with source that passes beskid analyze. To run test items, select a project with a valid .bproj manifest and a Test or Lib target.

Actions

1. Analyze one source file:

   beskid analyze Main.bd --plain

2. Build a debug executable:

   beskid build Main.bd --kind exe --plain

3. Build an optimized executable when you need a release artifact:

   beskid build Main.bd --kind exe --release --plain

4. Execute the same entrypoint in an AOT-compiled subprocess:

   beskid run Main.bd --entrypoint Main --plain

5. Run test items for a selected project target:

   beskid test --project App.bproj --target AppTests --plain

6. Select tests with --include-tag, --exclude-tag, --group, or --all-targets. The last option runs every Test target in one project process.

Expected result

The build command prints the object path and final output path. The run command returns the subprocess status. The test command reports passed, failed, skipped, and filtered items; it fails when a selected test fails.

Recovery

Treat the first error as the active failure. Fix analysis errors before code generation. A target-selection error requires a valid .bproj target name. A runtime-kit error requires a kit whose target and debug or release profile match the build. Do not select both --prefer-static and --prefer-dynamic.

Next task

Run the same gates in CI or read Projects before you add targets and dependencies.