commit | 05bea52ed3159aa5d15d967f5f56fc084a2b6c73 | [log] [tgz] |
---|---|---|
author | John Cater <jcater@google.com> | Tue Oct 17 08:07:05 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 17 08:08:05 2023 -0700 |
tree | acfac04d62efcb1bf8ed7921f841375ca6e2e0a2 | |
parent | eeb9c911bf16271f807c687e8eae246edaecd005 [diff] |
Enable Android Platforms by default for Android-related builds Fixes #16285. RELNOTES: Enable Platforms and Toolchains for Android. Android projects will need to stop passing the legacy flag `--fat_apk_cpu`, and instead use `--android_platforms` using platforms defined with the `@platforms//os:android` constraint. The https://github.com/bazelbuild/rules_android repository defines four standard Android platforms for projects that use those rules, `@rules_android//:armeabi-v7a`, `@rules_android//:arm64-v8a`, `@rules_android//:x86`, `@rules_android//:x86_64`. Blog post describing these changes to follow. Closes #19726. PiperOrigin-RevId: 574153852 Change-Id: Ief1e1be95fa03dd038a912dd318628ffdd562eaa
{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