| commit | d4e673ed93aa34dc20c3fb0d1a01f713cf6a7258 | [log] [tgz] |
|---|---|---|
| author | Laszlo Csomor <laszlocsomor@google.com> | Thu Jun 29 18:02:52 2017 +0200 |
| committer | Marcel Hlopko <hlopko@google.com> | Fri Jun 30 12:59:43 2017 +0200 |
| tree | 7bdc9e34fba5407df72538d131bb1371b27992e4 | |
| parent | 17770e5d78e640e419194504293df563d77ccf8c [diff] |
Android tooling: host/target path distinction Introduce host and target path separation in the Android incremental_install.py. This will allow running this script (and use bazel mobile-install) on platforms with non-POSIX path semantics (e.g. Windows). See https://github.com/bazelbuild/bazel/issues/3264 Change-Id: If6ec09f100dd2e0be3389dce25cb1a13305226e9 PiperOrigin-RevId: 160531950
{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.