| commit | e4fbf4236fa1606accc24918aa95abc4fb3b4b8e | [log] [tgz] |
|---|---|---|
| author | László Csomor <laszlocsomor@google.com> | Tue Feb 28 16:14:32 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Tue Feb 28 17:02:58 2017 +0000 |
| tree | 09d04ee9930927af0fce35b227dbde4a37b2cfc7 | |
| parent | 40668140e7539ee1ae3b14bf10b6513c158b5096 [diff] |
Bazel client: make some libraries visible to ijar Ijar will use Bazel's file handling logic so that we don't have to maintain two implementations, and don't have to copy this code to implement the Windows/MSVC code path in third_party/ijar/platform_utils.cc. See https://github.com/bazelbuild/bazel/issues/2157 -- Change-Id: Iec327febb882aeaabae55216d0d06488f7c151ed Reviewed-on: https://cr.bazel.build/9068 PiperOrigin-RevId: 148770951 MOS_MIGRATED_REVID=148770951
{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.