| tag | 9b61dc02dbbf8e7c32d1243d2899cdefbc1d518c | |
|---|---|---|
| tagger | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 16:53:36 2016 +0200 |
| object | f96c5c84f314200820fdac575a920f97dff870bb |
0.2.2 0.2.2 Release 0.2.2 (2016-04-14)
Baseline: 759bbfe
Extra cherry picks:
+ 068a661: GPLv2 + Classpath exception compliance: ship the source code of jformatstring
+ a18add1: Adds the source of the checker framework
+ f6c24de: GPLv2 + Classpath exception compliance: ship the source of checker_framework
+ c95cb5f: Add source for Javac
+ 4017d28: Fix fallout of incorrectly merged review (3921)
+ 1250fda: Rollback of commit
351475627b9e94e5afdf472cbf465f49c433a25e.
+ ba8700e: Correctly set up build variables for the correct pic
mode for fake_binary rules.
+ 386f242: Automated [] rollback of commit
525fa71b0d6f096e9bfb180f688a4418c4974eb4.
New features:
- --extra_entitlements allows passing additional entitlements for
iOS signing
- The output of -printconfiguration of proguard is available
through an implicit "[target_name]_proguard.confg" output of
android_binary (and
java_binary).
- Objective-C compiler information is now available to Skylark.
Important changes:
- ProGuard relies on bazel to check to see if the inputs have
changed.
- Build the jsonnet tool for the host when cross-compiling.
- Add ProductType for watch OS 1 extension and application.
- Restrict file types used for "entitlements" attribute to
[".entitlements", ".plist"]
- Restrict file types allowed for "strings" attribute to ".strings".
- local_repository can take a relative path.
- Support apple_watch1_extension and apple_watch_extension_binary
rules for creating watch OS 1 extensions.
- implement list.insert for skylark rule
- Enable overriding attributes for Rust binaries.
- ios_device attribute "xcode", for declaring a specific xcode to
use when selecting iOS simulators.
| commit | f96c5c84f314200820fdac575a920f97dff870bb | [log] [tgz] |
|---|---|---|
| author | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:00:12 2016 +0200 |
| committer | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 13:00:12 2016 +0200 |
| tree | 1fd8f8068095c0b1cebecfa071e40bbdefa2323f | |
| parent | 4f66e0942a3ebbb1f04257d7aea8a4d3272a5625 [diff] |
Updated CHANGELOG with source cherry-picks
{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.