| commit | 3875712ca6cabaa447b008038225072ee52b24c2 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Dec 01 17:12:58 2016 +0000 |
| committer | Irina Iancu <elenairina@google.com> | Fri Dec 02 07:42:13 2016 +0000 |
| tree | 4e6979226d374874d0b77a75ceeab1048d2ee606 | |
| parent | c804c66856eefc72cc1c5ba661c6d410e1bda9f4 [diff] |
Compute module file compile command line flags right before executing the action. This removes flattening of nested sets (for the transitive/top-level header modules) in the analysis phase making it about 10% faster. Also remove the calculation of top-level modules entirely as it doesn't seem to be necessary and doing it might actually lead to unexpected results when actions are restored from cache and thus the module input flags are computed from the actually used inputs (determined from .d files). -- MOS_MIGRATED_REVID=140738461
{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.