| commit | ca0b20eb1b5f381c04ad2fad8e87d9fd66a48fe4 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Nov 21 10:50:19 2016 +0100 |
| committer | László Csomor <laszlocsomor@google.com> | Mon Nov 21 10:50:19 2016 +0100 |
| tree | 3265a20a57dc3cefd79c1dffaa4e7fd6cb4ca031 | |
| parent | 38321ed2dd79ba2f1ede838d05ab924cac58e87a [diff] |
Release 0.4.1 (2016-11-21)
Baseline: 9a796de
Cherry picks:
+ 88bfe85: Description redacted. -- MOS_MIGRATED_REVID=139219934
+ b09ea94: Rollback of commit
a3f5f576cd35798140ba3e81d03d919dd4ecb847.
New features:
- android_library now has a "exported_plugins" attribute just like
java_library
- Use --strict_system_includes to apply hdrs_check=strict also to
cc_library.includes, even if sandboxing is disabled.
- Bazel on Windows: java_binary can now be the executable of
Skylark rule actions (ctx.action's executable argument)
- Packages are defined in BUILD.bazel as well as BUILD files.
Important changes:
- getattr()'s 3-arg form no longer raises an error when the
retrieved field is a built-in method.
- --apk_signing_method default changed to v1. Android APKs are now
signed with the new ApkSignerTool by default.
- New rule: proto_lang_toolchain(), to support LANG_proto_library
rules on multiple platforms.
- Fix for Android clang++ std::stack segfault on 32bit x86. See
https://code.google.com/p/android/issues/detail?id=220159
- Default android_manifest_merger is now "android" which uses the
official Android manifest merger.
http://tools.android.com/tech-docs/new-build-system/user-guide/man
ifest-merger
- Do not propagate aspect to its own attributes when using '*'.
- Comparing sets (`if set1 < set2:`) is not allowed anymore in
Skylark because it didn't work correctly anyway.
- When --experimental_extra_action_top_level_only, Bazel reports
extra-actions for actions registered by Aspects injected by a
top-level rule (approximately).
- Blacklists for proto_lang_toolchain() no longer have to be
proto_library's.
- Extra actions now contain aspect-related information.
- Fix slicing bug where "abc"[:-4:-1] would give wrong answer
{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.