| commit | bc3c57df6a561de7fd021e388705c88c82ebee34 | [log] [tgz] |
|---|---|---|
| author | Carmi Grushko <carmi@google.com> | Wed Feb 08 16:44:36 2017 -0500 |
| committer | Kristina Chodorow <kchodorow@google.com> | Thu Feb 09 16:53:32 2017 -0500 |
| tree | b55d222191d88424a71d225e50de1566cf66a4d2 | |
| parent | 50e7e7f89a985de944e8b966ee0f827b39c91666 [diff] |
Rearrange third_party/protobuf/BUILD to look like the upstream protobuf repo 1. Removed "protobuf" which used to point at the Java proto runtime. 2. Added "protobuf" that points at the C++ proto runtime (protobuf_clib also currently points there) 3. Added "protobuf_java_util" which points at Java proto utils (protobuf-util also currently points there) 4. Removed some aliases which aren't used in Bazel. Change-Id: If23a9797af8d87fd6df89bf9bad361288f2e0565
{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.