Prebuilt binaries for 18 targets. Unzip one, run hover --setup to build the runtime against a Zig toolchain, and you're compiling circuits — no source checkout, no build system to assemble by hand.
The archive carries the compiler, the runtime sources and the standard library. --setup does the rest.
$ unzip hover-v0.8.0-linux-x86_64.zip
$ cd hover_v0.8.0_linux_x86_64
$ ./hover --setup
$ ./hover my_circuit.hvrZig must already be on your PATH — --setup reports it rather than downloading one. Install it from your package manager or ziglang.org, then re-run.
> tar -xf hover-v0.8.0-windows-x86_64.zip
> cd hover_v0.8.0_windows_x86_64
> hover.exe --setup
> hover.exe my_circuit.hvrNo prerequisites. --setup downloads a Zig toolchain into .\toolchain\zig beside the binary, so nothing is installed system-wide.
Hover v0.8.0
[Setup] Zig found on PATH: /usr/bin/zig
[Setup] Compiling 16 runtime sources with /usr/bin/zig...
[Setup] Runtime built: runtime/build/libhover_runtime.a (zig 0.16.0)
[Setup] Warming Zig's C++ link cache...
[Setup] Done — hover is ready to use.It resolves the toolchain, compiles the bundled Eigen-based MNA runtime into a static library, and primes Zig's link cache so your first real compile isn't the slow one. Run it once per extracted release — or any time a build fails with Zig not found.
Every archive contains the same tree: the hover binary, runtime/ (Eigen + the C-ABI headers) and standard_library/. Statically linked — no shared-library hunt.
Checksums and release notes live on the GitHub release page. macOS builds aren't published yet — build from source in the meantime.
$ git clone https://github.com/eraymerc/hover-lang.git
$ cd hover-lang
$ make buildNeeds Go (the compiler itself) and Zig (which compiles the generated sim.cpp and the runtime — Eigen is vendored, so there's no separate C++ dependency to install). See the install docs for target-specific make directives.