Qu

Download

One binary, no runtime to install. Releases are built and published by CI for every platform below.

Binaries

PlatformTargetPackage
Windows (Intel / AMD)x86_64-pc-windows-msvc.zip and -setup.exe
Windows on ARMaarch64-pc-windows-msvc.zip and -setup.exe
Linux (Intel / AMD)x86_64-unknown-linux-gnu.tar.gz and .deb
Linux on ARMaarch64-unknown-linux-gnu.tar.gz and .deb
Linux, any distributionx86_64-unknown-linux-musl .tar.gz, statically linked
macOS (Apple silicon)aarch64-apple-darwin.tar.gz

There is no separate macOS Intel command-line build: its CI runner was never scheduled, so it was dropped from the release matrix. Intel Macs can build from source (below) or use Qu Studio's universal macOS app.

Latest release What changed

The Windows -setup.exe installs qu for the current user (no admin prompt) into %LOCALAPPDATA%\Programs\Qu and adds it to the user PATH. /S installs silently, /D=<folder> (last) picks the folder, /ALLUSERS installs machine-wide. Uninstall from Settings → Apps or with uninstall.exe /S; it removes only its own files and PATH entry.

Every release carries SHA256SUMS. The static musl build is the one to reach for on an older enterprise distribution or in a minimal container — it depends on nothing.

Qu Studio, and qu on your PATH

Qu Studio installers are on the same release page and bundle their own qu binary. Only one of them makes that qu usable from an ordinary terminal.

PackagePuts qu on PATH?
Qu Studio for Windows, …_x64-setup.exe Yes, for your user account. Its install folder, which holds qu.exe, is added to your user PATH; the uninstaller removes exactly that entry. Open a new terminal afterwards.
Qu Studio .msi, macOS .dmg, Linux .AppImage, .deb, .rpm No. The bundled qu is for Studio's own use; install a command-line build from the table above as well.
Command-line .zip / .tar.gz No. Unpack it and add the folder to PATH yourself.
Command-line .deb Yes. It installs qu into /usr/bin.

The Windows setup also copies Qu syntax support into VS Code, Sublime Text and Notepad++ if it finds that editor's settings folder, and skips it silently otherwise. See Editors for manual installs.

iPad and phones

Not yet, and it is worth being specific about why rather than leaving it off the list.

iPadOS / iOS

Needs an app, or a browser build

iOS has no terminal and no subprocesses, so a command-line binary is not a thing that can be installed. The routes are an app with the engine embedded, or compiling the interpreter to WebAssembly and running it in Safari. The WebAssembly crate today wraps only the numeric core, so neither is done.

Android

Works under Termux

The Linux ARM64 build runs in Termux today. There is no packaged app.

From source

Rust stable, and nothing else. The optional GPU and deep-learning backends are feature flags and off by default.

git clone <repository>
cd qu
cargo build --release --manifest-path engine/Cargo.toml

engine/target/release/qu run examples/hello.qu
engine/target/release/qu repl