| commit | 760d1f54a3889d64c81f2caa6f253f3d6e6c8109 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon Sep 28 15:05:34 2015 +0000 |
| committer | Florian Weikert <fwe@google.com> | Wed Sep 30 09:31:08 2015 +0000 |
| tree | af3b7b96d661a1e82ec39c05b50097204a79c2af | |
| parent | 0113352ad8c5653d04af7bcbd7b1225000652ab3 [diff] |
Adds the textual_hdrs attribute, which are treated as regular headers but not currently included in the module map. On Xcode 7, we should add them to the module map as additionalExportedHeaders, since it supports the textual keyword. RELNOTES: Add support for objc textual headers, which will not be compiled when modules are enabled. -- MOS_MIGRATED_REVID=104100551
{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.