| commit | 36355da02cfbfd1ab8361309543a4f4a4f8f9c7a | [log] [tgz] |
|---|---|---|
| author | jfield <jfield@google.com> | Mon Apr 17 18:24:53 2017 +0200 |
| committer | Klaus Aehlig <aehlig@google.com> | Tue Apr 18 11:32:17 2017 +0200 |
| tree | a7daac4b87df2e12ec97bc04ce229e1d3a1d1cce | |
| parent | 70f5d58f0e3d581fbb2bbf821a21ef0b301e1f3c [diff] |
Automated g4 rollback of commit e7c730ba64d1c34ac7049f4165a33dc1329d0019. *** Reason for rollback *** breaks tests *** Original change description *** Extract --sysroot flag from bazel and move it into crosstool This is an encore of https://github.com/bazelbuild/bazel/commit/6127358c1799d8d83cebbd499edac89f869df41b . RELNOTES: None. PiperOrigin-RevId: 153351147
{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.