commit | c77eac95ffdee4f127e20266c41cb92cec2a8956 | [log] [tgz] |
---|---|---|
author | Yun Peng <pcloudy@google.com> | Wed Mar 08 13:54:06 2017 +0000 |
committer | Vladimir Moskva <vladmos@google.com> | Wed Mar 08 13:56:43 2017 +0000 |
tree | 80635cf6c897b7613d28bdbff6a68ae6ea95cc5e | |
parent | a1ea9963d33f87ed61739c72c495f73246119eea [diff] |
Make MSVC CROSSTOOL default on Windows The default C++ CROSSTOOL on Windows now becomes MSVC, --cpu=x64_windows_msvc is still supported To use MSYS toolcahin, add --cpu=x64_windows_msys and --host_cpu=x64_windows_msys for host compilation See https://github.com/bazelbuild/bazel/issues/2627 -- Change-Id: Ie788a39cb5ffbc9fc956ccfd51a3cc816c74543a Reviewed-on: https://cr.bazel.build/9292 PiperOrigin-RevId: 149530250 MOS_MIGRATED_REVID=149530250
{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.