Bazel 8.0

I would encourage anyone in doubt to give Bazel a try, especially for C/C++ projects. I find it to be very robust nowadays, and much saner than CMake or Makefiles. Even if you don’t have a huge monorepo, the reproducibility and speed are great.

Here&#x27;s my guide on when to use bazel, that I wrote back when I was at Earthly.<p>I think it&#x27;s still very representative.<p><a href="https:&#x2F;&#x2F;earthly.dev&#x2F;blog&#x2F;bazel-build&#x2F;" rel="nofollow">https:&#x2F;&#x2F;earthly.dev&#x2F;blog&#x2F;bazel-build&#x2F;</a>

Bazel makes easy things hard and impossible things possible

Did a crazy thing and adopted Bazel for our two person company. Took a while to get everything working, but the average build takes about 30 seconds to run, across Go &#x2F; Rust &#x2F; TypeScript.

I like layering Makefile on top of language-specific build tools like Go, Poetry, cargo, gradle and yarn.<p>Has anyone seen an advantage of using bazel? The learning curve is an issue as well.<p>Blaze (inside Google) was pretty good but not only because of common builds but also because of artifacts that were shared across developers.

Bazel is the most distro hostile build system I know.

I&#x27;ve been using it to package the opentelemetry-c++ sdk for us, with single command:<p>bazel run make_otel_sdk<p>it compiles debug, fastdebug, release, then it places the .dll, include&#x2F; folders, etc. into single zip. I&#x27;m also invoking sentry-cli to obtain all source code used and also place them in<p><a href="https:&#x2F;&#x2F;github.com&#x2F;malkia&#x2F;opentelemetry-cpp&#x2F;actions&#x2F;runs&#x2F;12055826824&#x2F;job&#x2F;33617036685#step:17:64">https:&#x2F;&#x2F;github.com&#x2F;malkia&#x2F;opentelemetry-cpp&#x2F;actions&#x2F;runs&#x2F;120...</a><p>it produced this<p><a href="https:&#x2F;&#x2F;github.com&#x2F;malkia&#x2F;opentelemetry-cpp&#x2F;releases&#x2F;tag&#x2F;v1.18.0-dll.1">https:&#x2F;&#x2F;github.com&#x2F;malkia&#x2F;opentelemetry-cpp&#x2F;releases&#x2F;tag&#x2F;v1....</a><p>At work in a top level .bazelrc I have caching on the intranet, but on the github I&#x27;m relying (not ideal) on the actions&#x2F;cache through disk_cache blobs - it works, but storing back all &quot;blobs&quot; makes it a bit worse than expected.

&gt; The WORKSPACE mechanism is now disabled by default.<p>&gt; Bzlmod, the new way to manage external dependencies, is turned on by default since Bazel 7.0.<p>&gt; We are aiming to remove WORKSPACE in Bazel 9 completely.<p>Oh, that&#x27;s good to know. Sorry I wasn&#x27;t paying attention, M.