| commit | 580cd692ead8e466c74255f26d9f860c0135f191 | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 11 05:37:26 2015 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Thu Jun 11 10:38:06 2015 +0000 |
| tree | 90c77ea577a1e44291aeccb6e313aa51f5143f07 | |
| parent | cae0a64a074b924e8882d4d79e12ed7be1b89bef [diff] |
Fix order of redirection in compile.sh This avoid having garbage warning when compiling Java code because we use the internal API of Javac. Also add a run_silent around the protobuf compilation. Fixes #239 -- MOS_MIGRATED_REVID=95707763
{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.
How to install Bazel
How to get started using Bazel
The Bazel command line is documented in the user manual
The rule reference documentation is in the build encyclopedia
How to use the query command
How to extend Bazel
The test environment is described in the test encyclopedia
About the Bazel project:
