| commit | ff47759a662c6e9664d3ed03836f73e2c0c6093f | [log] [tgz] |
|---|---|---|
| author | Chris Parsons <cparsons@google.com> | Mon Oct 31 17:53:27 2016 +0000 |
| committer | Laszlo Csomor <laszlocsomor@google.com> | Wed Nov 02 08:25:57 2016 +0000 |
| tree | 51bf355fd89c81636ba0d6c3fb3a1e8988dfad82 | |
| parent | a0e3af46ca41f55163188d4beef10534c006aaca [diff] |
Initial implementation of "dylib" attribute for apple_binary and apple_dynamic_library rules Provided values propagated from "dylib" dependencies will be compiled against the srcs of the rule, and linked together with the dependencies. It is worth noting that "dylibs" differs from "deps" in that there is no configuration transition along this edge. There is more work to be done on this attribute, so it remains undocumented. Namely, symbol deduping between dylib and statically-linked dependencies needs to be addressed. -- MOS_MIGRATED_REVID=137721599
{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.