01. It works on my machine (and yours, eventually)
Install the Beskid CLI, verify a release or local build, and run your first commands without ritual sacrifice.
It works on my machine (and yours, eventually)
Philosophy is optional. A compiler binary is not.
This chapter is the “get off Twitter and onto a terminal” track: downloads, PATH, building from source when you must, and the smallest smoke test that proves the toolchain is alive. Normative install contracts live on Downloads and in tooling manifests; here we stay practical.
Use Install Beskid for the verified installation, upgrade, pin, and uninstall procedure.
If you skipped Why Beskid Exists, nobody is judging you (much).
What you will find here
Section titled “What you will find here”| Section | Topic |
|---|---|
| Downloads and rolling releases | cli-stable / cli-unstable, version files, and what “rolling” means. |
| Install scripts and PATH | Platform install tabs, shell profile, and finding beskid. |
| Build from source | Compiler workspace, targets, and when CI binaries are not enough. |
| First smoke test | beskid --version, parse, analyze on a real .bd file. |
| Troubleshooting install | Wrong arch, stale PATH, corelib materialization, and other fun. |
By the end of this chapter
Section titled “By the end of this chapter”- You have a
beskidbinary on your PATH (or you know exactly why not). - You understand rolling CLI versioning vs pinning for CI.
- You can run a one-file parse/analyze without opening the compiler repo.
Start here
Section titled “Start here”Downloads and rolling releases — or jump straight to First smoke test if someone already installed the CLI for you.
Next chapter
Section titled “Next chapter”02. PATH not found — tooling anyway — editors, LSP, and the CLI surface you will live in daily.