commit | c18b687c21d716d62a9c4cf069eeddb7a80e1597 | [log] [tgz] |
---|---|---|
author | Googler <wyv@google.com> | Tue Apr 23 08:26:16 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 23 08:28:01 2024 -0700 |
tree | d73593b97630528ad5e41f6206ccc6c818ee41aa | |
parent | c900865bbb3c38b589d6e5fbc422d61d3bba4681 [diff] |
Revert `android_sdk_repository` to using `local_config_platform` The native repo rule `android_sdk_repository` used to load from `@local_config_platform//:constraints.bzl`; https://github.com/bazelbuild/bazel/commit/74c8ca4886cfc188d60a18e796743e842f675842 changed it to load from `@platforms//host:constraints.bzl`. This caused failures with WORKSPACE users, as `@platforms` might still refer to an old version of `platforms` which doesn't have the `host` package, even though `@local_config_platform` knows to redirect to the bundled, newer version of `platforms`. This CL reverts that change, so `android_sdk_repository` now loads from `@local_config_platform` again. This is fine because both are native repo rules and will be deprecated at the same time. Partially fixes https://github.com/bazelbuild/bazel/issues/21877. PiperOrigin-RevId: 627395814 Change-Id: I5761cde3c86190d6da3e3933aa1bef18e0dcca3e
{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