| commit | 22d3570c5ee212291d98e29cdccbe6ff350c7a38 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Nov 30 16:55:12 2016 +0000 |
| committer | Irina Iancu <elenairina@google.com> | Thu Dec 01 10:14:25 2016 +0000 |
| tree | 81d83cf4253c18aca3ff8b4dfa6f8f80c2f8ff1e | |
| parent | 6f8393f5c5bddbb49a74d3229411e1050d799208 [diff] |
Move the useHeaderModules member from CppCompilationContext into the CppCompileAction. It seems wrong to bind this to a context. Instead, we should be able to determine for each action, whether it can use modules or not. Also allow overwriting the value obtained by the feature configuration in the CppCompileActionBuilder. This can e.g. be used to disable modules in CppSemantics.finalizeCompileActionBuilder(), if modules cannot be supported under certain circumstances. -- MOS_MIGRATED_REVID=140610096
{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.