| commit | e116bae8213ca31ae590a60748c1b6d505a4f819 | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Wed Dec 06 03:25:38 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Dec 06 03:29:45 2023 -0800 |
| tree | 7957ad82c5e5788595fe9222d57cde599f59e99a | |
| parent | c5493b9557502fe6ec48e78b0b5f06f4c1d75238 [diff] |
Make incompatible_enable_cc_toolchain_resolution a no-op Make crosstool_top flag a no-op and remove the code used to retrieve toolchain from crosstool_top. Remove the tests related to crosstop or incompatible_enable_cc_toolchain_resolution. Those tests can't work anymore, becuase the functionality is removed. There are some further cleanups, like removing _cc_toolchain attribute from the rules. RELNOTES[INC]: incompatible_enable_cc_toolchain_resolution is a no-op, enabled by default (https://github.com/bazelbuild/bazel/issues/7260) PiperOrigin-RevId: 588363296 Change-Id: I8af466628ce9c8d9175533255faef36968570aa4
{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
