| commit | d53d10bfc61096158f3b7ee7e8aab2f782398716 | [log] [tgz] |
|---|---|---|
| author | Manuel Klimek <klimek@google.com> | Thu Aug 06 14:38:16 2015 +0000 |
| committer | David Chen <dzc@google.com> | Thu Aug 06 22:15:56 2015 +0000 |
| tree | fd8b25e56b95b5a8bf0c6f5bb900c7bd084f93f9 | |
| parent | 37428d23fb9a60ee74cc2ad2c50db045aa3bcbf5 [diff] |
Feature configuration: add a field required_variables on flag_sets. This allows to prevent expansion of flag sets based on whether build variables are available. If required_variables is not set, and a variable that is referenced in the flag_set's flags is not available, the build will fail. We need the new behavior when some input files (for example profile data in FDO enabled builds) are only available for a subset of the translation units of a given target. -- MOS_MIGRATED_REVID=100028996
{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.