| commit | ff30a7319fc495c1f2d4c58b233e7bd7690da27f | [log] [tgz] |
|---|---|---|
| author | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 09 11:15:34 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jun 09 11:27:23 2016 +0000 |
| tree | fddbd8f5740a618428ea0aa340bff778e56aade4 | |
| parent | cc993c26047f8d459711ed211338570ce7c1576c [diff] |
Turn --legacy_external_runfiles back on by default
--nolegacy_external_runfiles breaks $(location @repo//) syntax for the runfiles case. This will be fixed when the structure of external repository in the execroot will be the same as in the runfiles tree so let flip that flag back on.
Fixes #1356.
RELNOTES: Revert of commit bd69849378112c3b05bc218e57cdafca82860710, legacy runfiles tree paths are still
supported by default.
--
MOS_MIGRATED_REVID=124445792
{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.