| commit | b692917a73e73d05a65979992f87ad93445dee97 | [log] [tgz] |
|---|---|---|
| author | Klaus Aehlig <aehlig@linta.de> | Wed May 11 12:46:15 2016 +0000 |
| committer | Klaus Aehlig <aehlig@google.com> | Wed May 11 12:55:47 2016 +0000 |
| tree | e6f52d85d1eadd1c36108023c8a859c74c443cd0 | |
| parent | f16397f33108116119e28952660370fc2e9d67a3 [diff] |
Make create_embedded_tools.sh an sh script This script is called directly (and not as an argument to the shell), hence the #!-line needs to be correct. As the script does not use any bash-specific feature, we can maintain it as a script for the POSIX shell, which has the advantage that the path is canonical. -- Change-Id: Id1d1d0a4f4516c91fa25cf2402dda5190e618166 Reviewed-on: https://bazel-review.googlesource.com/#/c/3602 MOS_MIGRATED_REVID=122046234
{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.