| commit | dfef43621c6658ac695164db55c7da205dffc869 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri May 26 22:26:23 2017 +0200 |
| committer | László Csomor <laszlocsomor@google.com> | Mon May 29 14:07:58 2017 +0200 |
| tree | e462fabb73dafbf8966b8a2f8dfb5e86b73dd8fb | |
| parent | 77f12de356958b9beb99fa12d89fd74848a8aa90 [diff] |
Keep "srcs", "hdrs" and "textual_hdrs" separate. Each can has slightly different semantics for the IDE, and it is better to use the information on which files belong to which group from BUILD file rather than use heuristics like file extension to determine it. The contents of "textual_hdrs" are added by the prefetcher. RELNOTES: None. PiperOrigin-RevId: 157256048
{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.