| commit | 678bdeaf8ceb496cce3a3e63fbb9be6eb54c7888 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed May 04 20:23:12 2016 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Thu May 05 19:10:12 2016 +0000 |
| tree | e9228956d57993c8fe5a788ef0523f0b9fb5e447 | |
| parent | 799a82509438572e43a9b62e19890156d721c12f [diff] |
Provide .pcm files as input to LIPO builds. Previously, bazel would be internally inconsistent regarding whether it thought module files were in use for LIPO builds. The merged CppCompilationContext would not list .pcm files as inputs, because its useHeaderModules flag was forced to false, but the CppModel would expand %module_file to a list of .pcm files, because it thought that modules were in use. This results in LIPO build failures due to missing files. RELNOTES: Fix interaction between LIPO builds and C++ header modules. -- MOS_MIGRATED_REVID=121513092
{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.