Bazel

A link page of interesting libraries and utilities I found.

fshlib is a simple shell library for logging. It provides a set of functions to log messages with different severity levels.

The other day, I was pondering whether to keep setting particular bazel version in projects. I even removed some, to see what would become of it.

This repository provides Bazel rules for creating self-extracting archives (“shar"s) out of shell binaries.

The idea of this repository is to provide a hermetic, ephemeral and reproducible repository of prebuilt binaries, which can then be brought into bazel builds to remove the dependence on local binary installations.

This is another piece of news in my quest for hermetic, ephemeral, and reproducible builds (“HER”).

This is a collection of links to interesting articles and knowledge sources about the Bazel build system that I found.

This is another piece of news in my quest for hermetic, ephemeral, and reproducible builds (“HER”).

Update 2025-10-19: I made a searchable index of modules available from my registry at https://www.hdlfactory.com/bazel-registry.

lit2md is a simplistic literate programming (LP) converter.

In the world of reproducible builds and efficient dependency management, Bazel stands out as a powerful tool. However, fetching large or uncommon dependencies can sometimes be a bottleneck. Enter bazel_rules_bt, a set of Bazel rules that uses the BitTorrent protocol to bring decentralized file downloading capabilities directly into your build system.

This is a run-down of tips and tricks for the use of rules_nixpkgs, a rule set for bringing in nix packages for use in bazel.

Cross-posted from the original at https://github.com/filmil/bazel-rules-bid

Other formats:

Program your FPGA with a one-liner command. It’s a kind of magic.

This is something seldom known, and a very sharp corner to cut yourself on. But you really want to know if you are using nix.

I present to you https://github.com/filmil/bazel_rules_ghdl: a set of bazel rules for converting VHDL into Verilog.

This article assumes that you have bazel installed via the bazelisk method.

Here is how I install bazel. I use this installation method on all of my machines. I do not think it is practical to go about this any other way. It is implied in all of my writings about bazel.

The repository https://github.com/filmil/bazel_rules_gcc_riscv64_baremetal contains bazel rules that can be used for a hermetic bare metal GCC cross-compiler for a 64-bit RISC-V machine, running in M-mode.

This short note defines the notions of hermetic, ephemeral and reproducible software build, as used in my writing.

I bother with bazel.

If you are in a hurry, fast forward to https://github.com/filmil/bazel_local_nix

Perhaps obvious in retrospect, but it is not possible for a bazel build artifact to generate a named pipe in the filesystem.

TIM-011 was an 8-bit teaching computer that was ostensibly developed by IMP in what is now Serbia.

https://github.com/filmil/bazoekt

I discovered this trick recently, while trying (and mostly failing) to build a library.

TIM-011 was an 8-bit teaching computer that was ostensibly developed by IMP in what is now Serbia.

I was a bit hard pressed to find all the proper work attribution. Please let me know if you have data to contribute.

Often needed little bits of bazel knowledge that I tend to forget.

Here is an example python Flask app built with Bazel. See README.md for instructions.

Adapted from the bazel-discuss mailing list.

The bazel build system has rules available to build C or C++ code from external repositories that use other more “conventional” build tools. By this I mean the usual suspects: GNU autotools, GNU make and cmake.