| commit | 6c07525462062d491816a66a94c3db3b2dbc8f98 | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Thu Jun 01 12:35:47 2017 +0200 |
| committer | László Csomor <laszlocsomor@google.com> | Thu Jun 01 14:09:06 2017 +0200 |
| tree | 2acea2b3688bf48d58ed426c060618fa51952276 | |
| parent | a4697fdc1372adc6189abda0990e9ffd7ed00d63 [diff] |
Windows: Create a dangling junction when symlink target doesn't exist On Unix system, `ln -s foo bar` will create an dangling symlink bar -> foo even foo doesn't exist. The current implementation of createSymbolicLink for Windows fails in this situtation. And this lead to #2474. In this change, we create a dangling junction when the target doesn't exist which mimics the behavior on Unix. Fixed https://github.com/bazelbuild/bazel/issues/2474 Change-Id: I442ca3e2fb20b76c9b5bbfee903299fe51481f43 PiperOrigin-RevId: 157694631
{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.