| tag | 1f1efc825086d58965afe781f8d85dfefaad8b55 | |
|---|---|---|
| tagger | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 16:55:40 2016 +0200 |
| object | da8331dcf1f2efcef799c7ca2b2aa7cec333f089 |
0.3.0 0.3.0 Release 0.3.0 (2016-06-10)
Baseline: a9301fa
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)
+ ff30a73: Turn --legacy_external_runfiles back on by default
+ aeee3b8: Fix delete[] warning on fsevents.cc
Incompatible changes:
- The --cwarn command line option is not supported anymore. Use
--copt instead.
New features:
- On OSX, --watchfs now uses FsEvents to be notified of changes
from the filesystem (previously, this flag had no effect on OS X).
- add support for the '-=', '*=', '/=', and'%=' operators to
skylark. Notably, we do not support '|=' because the semantics
of skylark sets are sufficiently different from python sets.
Important changes:
- Use singular form when appropriate in blaze's test result summary
message.
- Added supported for Android NDK revision 11
- --objc_generate_debug_symbols is now deprecated.
- swift_library now generates an Objective-C header for its @objc
interfaces.
- new_objc_provider can now set the USES_SWIFT flag.
- objc_framework now supports dynamic frameworks.
- Symlinks in zip files are now unzipped correctly by http_archive,
download_and_extract, etc.
- swift_library is now able to import framework rules such as
objc_framework.
- Adds "jre_deps" attribute to j2objc_library.
- Release apple_binary rule, for creating multi-architecture
("fat") objc/cc binaries and libraries, targeting ios platforms.
- Aspects documentation added.
- The --ues_isystem_for_includes command line option is not
supported anymore.
- global function 'provider' is removed from .bzl files. Providers
can only be accessed through fields in a 'target' object.
| commit | da8331dcf1f2efcef799c7ca2b2aa7cec333f089 | [log] [tgz] |
|---|---|---|
| author | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 10:52:57 2016 +0200 |
| committer | Dmitry Lomov <dslomov@google.com> | Tue Jul 12 10:52:57 2016 +0200 |
| tree | 27afea8ea4e7ea8857dc96d9ed6e593d5908abb2 | |
| parent | 0915764bbaa848e1a9b4a41d5d7627ee39779ed3 [diff] |
Upfated 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.