| commit | 95a4dd0269d95a2a5dc8a952573ef6d83791bbfb | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Tue Mar 14 11:24:01 2017 +0000 |
| committer | Yun Peng <pcloudy@google.com> | Tue Mar 14 19:49:56 2017 +0000 |
| tree | 1b4218c206c2fa45abaf28d0466f9a9d68082bd4 | |
| parent | ae84395a5bee2a04978335f0e08ce714f134d270 [diff] |
A partial, manual rollback of commit 7af14dfdbd6addb779226c0a103b2a8dc72c16b1. This became necessary because extra actions for C++ compile actions require .h files, but the compiler only returns the .pcm files in the .d file for headers that it reads from the .pcm file. This is not a problem for correctness because the .pcm files depend on the headers, but that doesn't help the extra actions that would then only get the .pcm files. -- PiperOrigin-RevId: 150052839 MOS_MIGRATED_REVID=150052839
{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.