| commit | 3b9423ddb9710a27504ddb554ad06696f6954550 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Wed Oct 14 12:11:51 2015 -0400 |
| committer | Damien Martin-Guillerez <dmarting@google.com> | Tue Nov 10 16:00:35 2015 +0100 |
| tree | 8b277ad443ffc52162ed30627b92f5bbb2319fda | |
| parent | 5a2fdb123e4924b340cc19568f5fe39bf01e6ea4 [diff] |
Release 0.1.1 (2015-10-05)
Baseline: 22616ae
+ 1ef338f: Rollback of "Propagates cc_library linkopts attribute
to dependent objc_libraries.": breaks certain
objc_binary build targets.
+ 5fb1073: Reintroduce an inconsistency check (albeit, in a weaker
form) removed by a previous change that was trying to
optimize away a filesystem call.
+ 6d00468b2eb976866cfb814d562e0d53a580a46f: Add IdlClass to the embedded default android tools
repository and rearrange BuildJar's JarHelper so that
it too can be embedded.
+ a5199039934a2e399a7201adc0d74e2f2d2b0ff3: Fixes Android integration tests by wiring up idlclass
rules in integration environment.
Incompatible changes:
- Bazel requires JDK 8 to run.
- Attribute "copts" is removed from j2objc_library.
New features:
- a cc_binary rule may list '.s' and '.asm' files in the srcs
- Support for build with libsass.
- labels in "linkopts" may match any label in either "deps" or
"srcs" to be considered valid.
- Maven servers that require username & password authentication are
now supported (see maven_server documentation).
Important changes:
- Support empty plist files
- The <compatible-screens> section of the AndroidManifest.xml will
not be overwritten if it already contains a <screen> tag for each
of the densities specified on the android_binary rule.
- Add Jsonnet rules to Bazel
- Remove deprecated xcode_options flag.
- Workspace names are now restricted to being in their base
directory
(that is, the names cannot contain up-level references or /./).
- j2objc_library on Bazel now transpiles transitive proto_library
dependencies. (Note that java_* rules in Bazel do not yet support
protos; currently they ignore proto dependencies.)
- new_http_archive can specify a root directory.
- Adds support for dylibs on devices for Xcode 7.
- [d] d_docs rules now depend on a d_binary, a d_library or
d_source_library.
- [docker] docker_build now set the permission to 0555 to files
added to the layer, use `mode = "0644"` to use the legacy behavior.
- android_binary now has a main_dex_proguard_specs attribute to
specify which classes should be in the main dex.
- [rust] Add rust_docs rule for generating rustdoc.
Change-Id: Id42f6cbeed9531c7023b754e6213782487650c44
{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.