| commit | 03f78f55a50fe2a2202b0b2cc46697faa2869533 | [log] [tgz] |
|---|---|---|
| author | Laszlo Csomor <laszlocsomor@google.com> | Wed Jun 14 15:46:05 2017 +0200 |
| committer | Yun Peng <pcloudy@google.com> | Wed Jun 14 16:21:05 2017 +0200 |
| tree | 184d6727e8c3916b670bb763b6a97f35eeceba0f | |
| parent | ba69b39468954ed382dc50bc3fc22a1446c5f9d8 [diff] |
Windows, bootstrapping: fix bootstrap_test Compute the --host_jvm_args for the bazel.windows_unix_root JVM flag on Windows. After commit 9c54e2a764f0ddd2d3787aade1c530c5f43bd26c it's the Bazel client's job to compute this JVM flag and pass to the server, but during bootstrapping we run Bazel in a client-less mode. Fixes https://github.com/bazelbuild/bazel/issues/3186 Change-Id: I2facfdef7d301d8a96213b488728e3ae6aec1c33 PiperOrigin-RevId: 158972256
{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.