| commit | 25b952b8fec4a3e514b4f91fbbd5e5133fcab4b7 | [log] [tgz] |
|---|---|---|
| author | Dmitry Shevchenko <dmishe@google.com> | Tue Oct 04 01:16:16 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Oct 04 08:56:38 2016 +0000 |
| tree | a77991ffd27f0283edecc9307ff8e51536a1fd6a | |
| parent | deeeb31f8ba0f196fbc9ca2a177d59d57ea50b32 [diff] |
Rollback of commit deeeb31f8ba0f196fbc9ca2a177d59d57ea50b32. *** Reason for rollback *** Breaks builds with current blaze *** Original change description *** Add a way to select non-default Xcode toolchain * Adds a flag --xcode_toolchain which sets TOOLCHAINS env variable for xcrun. * Updates swift_library to work with this flag when selecting Swift runtime location. * By default the flag has a null value and is not set in env. -- MOS_MIGRATED_REVID=135053864
{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.