Pack all multi-arch libraries from aar_import deps when using --fat_apk_cpu Currently if `--fat_apk_cpu` is specified with more than one architecture and there are `aar_import` dependencies containing shared libraries for multiple architectures, android_binary will only pack one of the shared libraries. This is because it's unaware of the split transition during artifact discovery. RELNOTES: Fixed an issue with Android builds where `--fat_apk_cpu` doesn't pack all selected shared libraries from `aar_import` targets into the APK. See [#8283](https://github.com/bazelbuild/bazel/issues/8283). Fixes https://github.com/bazelbuild/bazel/issues/8283 Closes #8510. Change-Id: I5432aff47310c4ca8881d41be226829c98254ea5 PiperOrigin-RevId: 250776117
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.