| commit | 97eaf9136abad30827cf1a060cc32e786745923d | [log] [tgz] |
|---|---|---|
| author | Lukacs Berki <lberki@google.com> | Thu Oct 15 12:06:12 2015 +0000 |
| committer | Lukacs Berki <lberki@google.com> | Thu Oct 15 12:28:54 2015 +0000 |
| tree | e7ddcef93712bf8cc0cb4031a5916d201ae548a3 | |
| parent | 3bb1990892d1bfb5a4e793431cb4730a3c0a06e6 [diff] |
Add a //src:bazel-notools target that is the same as the Bazel binary except without the embedded tools. Its use requires the addition of a local_workspace(name = "bazel_tools", path=...) to the WORKSPACE file. It is useful if you don't care about the set of embedded tools (because you provide them to Bazel in another way anyway) but you do care about the size of the Bazel binary (it's 16 MB compared to 56 MB with the tools). -- MOS_MIGRATED_REVID=105499508
{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.