Install bsc with Homebrew, MacPorts, Nix

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• bluetcl
• bsc

Project history

The BSC README says the toolchain was developed by Bluespec Inc. for almost 20 years before becoming the community-maintained open-source compiler under the B-Lang organization. That history matters because Bluespec is not a toy HDL: the README points to production designs such as Flute, Piccolo, and Shakti as evidence of prior industrial and academic use.

BSC supports two interchangeable syntactic flavors, Bluespec SystemVerilog and Bluespec Haskell/Classic. Its core language feature, Guarded Atomic Actions, lets designers describe modular rules and leaves scheduling work to the compiler. The packaged executable `bsc` emits standard Verilog, while `bluetcl` exposes Tcl scripting around the toolchain.

Adoption history

The upstream README lists distribution packaging for Arch AUR, Fedora via Terra, Gentoo GURU/LiGurOS, Homebrew, and Nix/NixOS. The provided package facts also show Homebrew, MacPorts, and Nix packaging, so the compiler has escaped source-only installation despite its niche hardware-design audience.

BSC adoption is concentrated in hardware language, RISC-V, and research communities rather than general software development. Its packaging is valuable because HDL compilers are often difficult to build reproducibly, and a package-manager formula lowers the cost of trying existing Bluespec designs.

How it is used

Users compile BSV or BH source with `bsc`, use the bundled Bluesim simulator for execution, use standard libraries documented in the BSC library guide, and can automate workflows through `bluetcl`.

Because BSC emits standard Verilog, it fits into existing synthesis and simulation flows rather than requiring a wholly separate downstream hardware ecosystem.

Why package nerds care

BSC is package-nerd significant because it packages a full hardware-description-language compiler, simulator, standard library, and documentation set into ordinary developer package managers. That is much rarer than another linter or HTTP client.

It also represents a long-lived proprietary/research toolchain becoming open infrastructure. For maintainers, the interesting parts are large binary/source builds, generated documentation, and keeping a specialized compiler available across general-purpose package ecosystems.

Timeline

• 2000s-2010s: Bluespec Inc. develops the toolchain for almost 20 years before the current open-source community phase.
• 2020: BSC is available through Nix/NixOS according to the upstream README's package list.
• 2020s: The B-Lang organization maintains the open-source compiler, documentation PDFs, test suite, and release artifacts on GitHub.
• 2026: The README badge points at release 2026.01 and the provided package facts show Homebrew, MacPorts, and Nix packaging.

Related projects

• bsc-contrib is the companion repository for libraries and utilities that do not belong in the core compiler.
• BDW, the BSC Development Workstation, provides a graphical environment and source-level waveform viewing.
• Flute, Piccolo, and Shakti are cited by upstream as production or serious Bluespec designs.
• Verilog/SystemVerilog synthesis tools are downstream consumers of BSC output.

Sources

• https://github.com/B-Lang-org/bsc
• https://github.com/B-Lang-org/bsc/releases/latest/download/bsc_user_guide.pdf
• https://raw.githubusercontent.com/B-Lang-org/bsc/main/README.md
• source_facts.package-manager