| commit | df22958d81b78ae9edd0a0874e5595cfa189877c | [log] [tgz] |
|---|---|---|
| author | mstaib <mstaib@google.com> | Fri Mar 31 21:50:46 2017 +0000 |
| committer | Marcel Hlopko <hlopko@google.com> | Mon Apr 03 13:37:33 2017 +0200 |
| tree | 327d49dd80d23ce3ae821b2829e6b442fa711b93 | |
| parent | 94261751bf2babe093696c35208e09768e3fd05e [diff] |
Add isConfigMatcher property to rule classes. BuildConfiguration currently depends directly on the name of a rule class to see if it is config_setting. This creates a circular dependency between ConfigSetting and BuildConfiguration. As ConfigSetting is being moved to rules/config, this circular dependency will no longer work. This replaces the name special case for a special property of the rule class, which only config_setting should set. RELNOTES: None. PiperOrigin-RevId: 151871084
{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.