| commit | a45939bba2e85eb5f5941033e37dc2d6f8e87489 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Apr 14 18:57:42 2017 +0200 |
| committer | Klaus Aehlig <aehlig@google.com> | Tue Apr 18 11:26:51 2017 +0200 |
| tree | c4995030d7c0150b15ebaa16943bef6d626c183b | |
| parent | 1341e3ed45045b85cda2c57c0623dae0d7149b16 [diff] |
In android_library targets, R.class files should not be runtime dependencies android_binary targets have their own R.java files (built from merging dependencies and any resources that belong directly to the target). As such, they don't need inherited R.java files at runtime. Taking these out makes for smaller APKs and less inheritance from the target's dependencies. Add a flag to control this behavior. Have it default to continue to include R.class files as runtime dependencies so we can control rollout of this behavior. Add tests of android_binary to ensure the JAR is filtered out as appropriate, and of android_robolectrictest to ensure that those tests still have access to the JARs. RELNOTES: none PiperOrigin-RevId: 153177074
{Fast, Correct} - Choose two
Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:
A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.
An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.
Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.
Find more background about Bazel in our FAQ.