commit | 1c3a2456c95fd19974a5b2bd33c5ebdb2b2277e4 | [log] [tgz] |
---|---|---|
author | Greg Estren <gregestren@gmail.com> | Tue Nov 23 12:17:08 2021 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 23 12:18:30 2021 -0800 |
tree | 928a46f5901c7ab21fce95425b60cd9184cb74bb | |
parent | 89ea68b0cb4a9f166f7dcfd00b031d7ba440dfb3 [diff] |
Support select() on constraint_value for aliases. This implements approach #4 of https://github.com/bazelbuild/bazel/issues/13047#issuecomment-805309450. The basic change adds a new toolchain resolution mode: "resolve iff the target has a select()". It then sets alias() to that mode. We could remove this special casing if we ever ubiquitously provide platform info to *all* rules (https://github.com/bazelbuild/bazel/issues/12899#issuecomment-767759147). RELNOTES: alias() can now select() directly on constraint_value() Fixes https://github.com/bazelbuild/bazel/issues/13047. Closes #14310. PiperOrigin-RevId: 411868223
{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