| commit | d470a32e641b0aa407ffbff2022f44636d204f67 | [log] [tgz] |
|---|---|---|
| author | schmitt <schmitt@google.com> | Mon Apr 17 20:31:13 2017 +0200 |
| committer | Klaus Aehlig <aehlig@google.com> | Tue Apr 18 11:33:10 2017 +0200 |
| tree | f24f9d195c95dcfdd0363b4522b4a95993cb70cf | |
| parent | 501b62716af12ba42c019bd9f231468b3c144757 [diff] |
Automated g4 rollback of commit e1d692e486a2f838c3c894fd9de693fabd6685ed. *** Reason for rollback *** broken tests *** Original change description *** Init absent action configs for CppCompile actions So far only link actions were initialized in CppLinkActionConfigs. This cl changes this class to also initialize CppCompile actions. This is needed for our ongoing work removing hard-coded flags from Bazel and moving them into Crosstool. RELNOTES: None. PiperOrigin-RevId: 153366563
{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.