commit | 75f8017ba3a87da4f593e37f0eb8f333b330d95c | [log] [tgz] |
---|---|---|
author | Guillaume Maudoux <guillaume.maudoux@tweag.io> | Mon Nov 06 08:04:15 2023 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 06 08:05:12 2023 -0800 |
tree | a39cf71a044cf9cd8588009157c637ce9e41313c | |
parent | 70f7c802582130861844026e1c1cc5ab5f922c24 [diff] |
Change `--extra_toolchains` precedence to last-wins, instead of first-wins. This only changes the precedence within all uses of `--extra_toolchains`, it does not change the precedence for `register_toolchains` calls. After this, the priority order for toolchains is: 1. Consider toolchains registered via `--extra_toolchains` 1. Within this set, the last mentioned toolchain has highest priority 2. Consider toolchains registered via `register_toolchains` 1. Within this set, the first mentioned toolchain has highest priority In all cases, pseudo-targets like `:all` and `/...` are ordered by Bazel's package loading mechanism, which is currently using a lexicographic ordering. Fixes #19945. Closes #19942. Closes #20031. PiperOrigin-RevId: 579845262 Change-Id: Ibd9c32e5479a6a27717734852b875f9b3f31b510
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md