| commit | af25cea3d0b2663226a3718fdfa619457a43a8b9 | [log] [tgz] |
|---|---|---|
| author | Thiago Farina <tfarina@chromium.org> | Wed Sep 28 08:59:38 2016 +0000 |
| committer | Yun Peng <pcloudy@google.com> | Wed Sep 28 09:18:26 2016 +0000 |
| tree | 076ee7d060b0df06708c5cb9eeb0d0717823cbea | |
| parent | 1047bbbb4a024ccc372f1464f8439764b233a1a8 [diff] |
cpp: reuse InWorkspace() function in GetWorkspace() The access() check in the do-while loop is basically doing the same thing that the InWorkspace() function provides. So lets just call that function instead. It also has the effect of making the code easier to read and understand. -- Change-Id: I02495775a9c9aa262396261824359538ca650e36 Reviewed-on: https://bazel-review.googlesource.com/#/c/6230 MOS_MIGRATED_REVID=134509465
{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.