| commit | 0e5b8b76595380fd3fa9e91e8f476917eecdb59b | [log] [tgz] |
|---|---|---|
| author | Chris Parsons <cparsons@google.com> | Thu Jul 28 18:26:25 2016 +0000 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Fri Jul 29 10:11:12 2016 +0000 |
| tree | f459ed8d5d35f2070321858c990f84eb77769140 | |
| parent | 7c38828e8cbca27e884db87bf80eda699f8527e4 [diff] |
Rollforward of change that broke #1579 with test fix (need to specify ios_sdk_version and xcode_version for our CI macs) *** Original change description *** Remove apple_binary's implicit output _lipo.a. This also removes the restriction that apple_binary targets must have at least one src file specified. -- MOS_MIGRATED_REVID=128721251
{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.