The Bazel team is happy to announce the release of version 0.11.0.
- android_binary targets built with ProGuard can now enjoy the benefits of incremental dexing by specifying the attribute
incremental_dexing = 1.
- aar_import rules now support importing assets from the
assets/subdirectory of the AAR being imported.
- Remote caching now supports HTTP Basic Authentication.
- You can now depend on
@bazel_tools//tools/runfiles:java-runfilesto get a platform-independent runfiles library for Java. See JavaDoc of Runfiles.java for usage information.
Here are some updates on what happened in the Bazel community over the past month.
Languages & Rules
- You can use Bazel to build Rust with rules_rust for the Rust compiler toolchain and cargo_raze to resolve Cargo.toml dependencies into WORKSPACE rules. See cargo_raze_crater for an example.
- Marcel Hlopko published the C++ rules roadmap, which is open for comments.
- Jay Conrod published a roadmap for the Go rules and Gazelle. If you are interested in contributing or have a question, head over to the bazel-go-discuss mailing list.
- VSCO released the latest version of their C++ CROSSTOOL using Chromium's LLVM toolchain.
- The Android build process involves many moving parts and can be complex. Alex Steinberg wrote here a detailed walkthrough on How Android Builds Work in Bazel.
- Justine Tunney made an experiment about turning a Bazel BUILD file into a Makefile using the results of bazel query.
- Nick Santos wrote a blog post on whether you should adopt Bazel for Go projects: Bazel is the Worst Build System, Except for All the Others
- Filip Nikolovski wrote an article about how InPlayer is Managing a Go monorepo with Bazel.
- Alex Eagle of the Angular core team did a 2-hour long deep dive of Angular's Buildtools Convergence (ABC).
- Kyle Cordes also gave a demo on building Angular applications with Bazel at Angular Lunch.
Did we miss anything? Fill the form to suggest content for a next blog post.