| commit | d700dff5152f5b76a50b6839a8ccc8c8c22e1f5d | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@google.com> | Wed Nov 23 16:53:22 2016 +0000 |
| committer | Dmitry Lomov <dslomov@google.com> | Wed Nov 23 17:02:52 2016 +0000 |
| tree | fe015027f187622579a4c4c6ea5f3d4e5b3ccd58 | |
| parent | 2c52dab02f37bb85ac8790823d613f8b6ae5358f [diff] |
Make compile.sh use pregenerated protoc output, if present Change ./compile.sh to look for pregenerated protoc output and use it, if present. If not, insist on PROTOC and GRPC_JAVA_PLUGIN to be specified via the environment. In this way compile.sh does not depend on committed binaries any more. -- Change-Id: I0d19a16535b606d2a6ab26ca349a7f9db8e224b7 Reviewed-on: https://bazel-review.googlesource.com/#/c/6731 MOS_MIGRATED_REVID=140037537
{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.