Write and run a program

beskid run analyzes the source, compiles it ahead of time, links an executable with the matching runtime kit, and runs that executable in a subprocess.

Prerequisites

Complete Install Beskid. Work in an empty directory where you can create a file.

Actions

1. Create Main.bd with this source:

i32 Main() {
    return 0;
}

2. Analyze the source:

   beskid analyze Main.bd --plain

3. Check its canonical format:

   beskid format Main.bd --check

4. If the format check reports drift, update the file before the next check:

   beskid format Main.bd --write
   beskid format Main.bd --check

5. Execute the program through the AOT pipeline:

   beskid run Main.bd --plain

6. Check the process status with the command that your shell provides. A status of 0 is success.

flowchart LR
  accTitle: Source to AOT execution
  accDescr: The CLI resolves and analyzes Main.bd, lowers it, compiles and links a native executable with the runtime kit, and then starts it as a subprocess.
  A[Main.bd] --> B[Resolve and analyze]
  B --> C[Lower]
  C --> D[AOT compile]
  D --> E[Link runtime kit]
  E --> F[Run subprocess]

Diagram text

1. The CLI resolves Main.bd and checks its syntax, names, and types.
2. The compiler lowers the checked program and emits native object code.
3. The linker uses the matching runtime kit to create an executable.
4. The CLI starts the executable as a subprocess and returns its status.

Expected result

Analysis completes without an error diagnostic. The format check exits successfully. The program prints no text and exits with status 0.

Recovery

If analysis points to the function name, use the exact default entrypoint Main. If formatting fails, run the documented --write command. If linking reports a missing or incompatible runtime kit, reinstall the same toolchain release; do not combine compiler and runtime files from different releases.

Next task

Connect the editor and language server, then use build, run, and test for development work.