| commit | a1dcae85919aec183a12624c9cfe603af92c89a1 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Wed May 08 14:27:11 2024 -0400 |
| committer | GitHub <noreply@github.com> | Wed May 08 18:27:11 2024 +0000 |
| tree | b8ce165fd48c939bcab5a82dc7672e62eaf6e5f4 | |
| parent | a01c443fbb18cd2a8c71d38516b4d4de14bf54fd [diff] |
[7.1.2] Set public visibility for R8 desugar binary (#22176) We are migrating Android functionality out of Bazel into rules_android. Currently rules_android depends on @bazel_tools//tools/android:desugar_java8 for a sh_binary that calls the R8 desugar binary. Going forward, we'll maintain the sh_binary directly in rules_android, and therefore will require public visibility on [...]/r8:desugar. Eventually the source code for the Bazel R8 desugar wrapper will also move into rules_android. Part of https://github.com/bazelbuild/rules_android/issues/122. Closes #21775. PiperOrigin-RevId: 618272641 Change-Id: I09d9ca19b742049c2d29a75336d1b0680b0005b1 Commit https://github.com/bazelbuild/bazel/commit/32fd6e9c2e7e4907c263ba8de2e55abd1484389b Co-authored-by: Ted Xie <tedx@google.com> Co-authored-by: Xùdōng Yáng <wyverald@gmail.com>
{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
