| commit | b7a731189eee8a57c6aee289f7b1bdae91b32d99 | [log] [tgz] |
|---|---|---|
| author | Andrew Pellegrini <apell@google.com> | Thu Jan 12 20:11:35 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Fri Jan 13 10:57:30 2017 +0000 |
| tree | 83aaca4fbb1e00d705a9bee83f2e2014d9a9e5bd | |
| parent | 748bbef68037ae57f973bdfe4405b3ccc3791574 [diff] |
Fix ResourceUsageModel analysis of <style> resource bugs by overriding this behavior in the extended class owned by ResourceUsageAnalyzer. This makes the fix available to both Blaze and Bazel, since Bazel uses the AOSP released version of the com.tools.android.lint library, which contains ResourceUsageModel, instead of the source version available in []. This change is based on the upstream patch [] and will be removed when the patch is included in the packaged version released with Bazel. -- PiperOrigin-RevId: 144355049 MOS_MIGRATED_REVID=144355049
{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.