commit | a3dedfc47b884ead416e3d3c91b675333d45da8e | [log] [tgz] |
---|---|---|
author | Dmitry Shevchenko <dmishe@google.com> | Thu May 26 18:12:53 2016 +0000 |
committer | Yue Gan <yueg@google.com> | Fri May 27 08:45:19 2016 +0000 |
tree | 449e0b9d0e0f1ad3c5ce3b6ee6ac9d120c1cfe28 | |
parent | b11e23c710df111169333b1b2d89744af6d751cb [diff] |
Add support for importing frameworks to swift_library. * Adds a way to read FRAMEWORK_ keys from ObjcProvider and provide outputs as -F args to the compiler * Adds a sample dynamic framework for testing RELNOTES: swift_library is now able to import framework rules such as objc_framework. -- MOS_MIGRATED_REVID=123337139
{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.