| commit | 09a3be927905f330ddc98c78bf4485ef2428caa0 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Jan 07 21:49:19 2016 +0100 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Thu Jan 07 21:49:19 2016 +0100 |
| tree | 81d84e3bfcc801c3696e6ad15bb7a1571cc4f904 | |
| parent | 4580e49ad88c74ced5c699edbed943aea482f498 [diff] |
Release 0.1.3 (2016-01-07)
Baseline: 23ad8f6
+ de2183d: Only depend on the WORKSPACE file for external files
that are under the external/ directory, i.e. were
created by Bazel.
+ f8f855c: Rollback of commit
12bad3af0eade9c4b79d76f9e1c950ad2e3214c2.
+ f627562: Stop parsing the WORKSPACE file when a parse error is
detected
+ 763f139: Add -fno-canonical-system-headers to CROSSTOOL files so
that gcc doesn't resolve symlinks in .d files, which
would confuse Blaze.
+ b95995b: Use openjdk7 as dependency for debian package of jdk7
flavor
New features:
- Skylark macros are now enabled in WORKSPACE file.
- .bazelrc allows workspace-relative imports as "import
%workspace%/path/to/rcfile"
- Evaluate the query expression in a file by passing
--query_file=<file> to query
Important changes:
- Remove obsolete --objc_per_proto_includes flag.
- iOS apps and extensions now have launch_storyboard
- Passing multiple JVM options via a single --host_jvm_args flag is
now deprecated. Pass each JVM option behind its own
--host_jvm_args flag.
- Resources defined locally on an android_library rule will respect
the neverlink attribute.
- Update Rust to 1.4
- Fix resource handling for exported android_library rules
- Files in external repositories are now treated as mutable, which
will make the correctness guarantees of using external
repositories stronger (existent), but may cause performance
penalties.
{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.