Choose how to run the course
Every tutorial with an editor can run in the browser. A local installation lets you save source files and invoke the command-line tool blyxc. Building a native executable also requires rustc and a host linker on the machine doing the build.
Download a release archive
Choose the Windows x86-64 ZIP, Linux x86-64 tarball, or Apple Silicon macOS tarball from the download page. Compare its SHA-256 digest with the entry for the same filename in SHA256SUMS. Extract the archive and add the directory containing blyxc to PATH. In PowerShell you can run .\blyxc.exe directly from the extracted directory.
Install with Homebrew
On Apple Silicon macOS or x86-64 Linux, the project tap installs the published compiler binary and checks the archive checksum.
brew install rahulchaube1/blyx/blyxInstall on Windows with Scoop
On Windows x64, add the project bucket once from PowerShell, then install the compiler and check its version. Scoop checks the release archive against the SHA-256 in the manifest. You can also install the native AI commands with scoop install blyx/linearfit blyx/residualwatch blyx/modelgate.
scoop bucket add blyx https://github.com/Rahulchaube1/scoop-blyx
scoop install blyx/blyx
blyxc --versionInstall with Cargo
With Rust, Cargo and a host linker installed, build the compiler from crates.io. The version flag selects the same release as this course. Cargo normally places the result in the bin directory under your Cargo home.
cargo install --locked --version 0.2.1 blyxcCheck your installation
Open a fresh terminal after a PATH change. The version command should print blyxc 0.2.1. If the shell cannot find it, check the directory from which the executable runs directly and make sure that directory appears on PATH.
blyxc --versionPractice
Confirm which compiler your terminal will use if you have both a downloaded binary and a Cargo installation.
Hint
Use Get-Command blyxc in PowerShell or command -v blyxc in a POSIX shell.
Worked solution
The path should point to the installation you intended. Run that path with --version to verify it before continuing.