4 ms·

From the bazel releases. It always starts with a binary.

• ryukafalz 6y ago
  I mean sure, you always need to start with a binary somewhere, but to put this into perspective... the binaries needed to bootstrap all the software on the distro I run on my laptop weigh in at about 60 MiB[0]. An x86_64 build of Bazel alone weighs in at about 27 MiB[1]. As someone who cares about source bootstrappability, that feels like sliding backwards. I suppose you may be able to find a chain of older versions of Bazel starting with one that doesn't require Bazel itself to build, like the Guix devs did for Rust[2]. [0] https://guix.gnu.org/blog/2020/guix-further-reduces-bootstrap-seed-to-25/ https://guix.gnu.org/blog/2020/guix-further-reduces-bootstra... [1] https://github.com/bazelbuild/bazel/releases/tag/3.5.0 https://github.com/bazelbuild/bazel/releases/tag/3.5.0 [2] https://guix.gnu.org/blog/2018/bootstrapping-rust/ https://guix.gnu.org/blog/2018/bootstrapping-rust/
  • laurentlb 6y ago
    There are two supported ways of building a Bazel binary. One uses an existing Bazel, this other uses a bash script that calls the compilers.
  • jnxx 6y ago
    And compare that to a few hundred bytes to bootstrap the whole Guix system.