0.5.4
Release 0.5.4 (2017-08-25)
Baseline: 6563b2d
Cherry picks:
- d4fa181:
Use getExecPathString when getting bash_main_file - 837e1b3:
Windows, sh_bin. launcher: export runfiles envvars - fe9ba89:
grpc: Consolidate gRPC code from BES and Remote Execution. Fixes
#3460, #3486 - e8d4366:
Automated rollback of commit
496d3de. - 242a434:
bes,remote: update default auth scope. - 793b409:
Windows, sh_bin. launcher: fix manifest path - 7e4fbbe:
Add --windows_exe_launcher option - 91fb38e:
remote_worker: Serialize fork() calls. Fixes #3356 - b79a9fc:
Quote python_path and launcher in
python_stub_template_windows.txt - 4a2e17f:
Add build_windows_jni.sh back - ce61d63:
don't use methods and classes removed in upstream dx RELNOTES:
update dexing tools to Android SDK 26.0.1 - 5393a49:
Make Bazel enforce requirement on build-tools 26.0.1 or later. - 5fac03570f80856c063c6019f5beb3bdc1672dee:
Fix --verbose_failures w/ sandboxing to print the full command
line - f7bd1acf1f96bb7e3e19edb9483d9e07eb5af070:
Only patch in C++ compile features when they are not already
defined in crosstool - d7f5c12:
Bump python-gflags to 3.1.0, take two - 3cb136d:
Add python to bazel's dockerfiles
New features:
- Do not disable fully dynamic linking with ThinLTO when invoked
via LIPO options.
Important changes:
- Ignore --glibc in the Android transition.
- Remove --experimental_android_use_singlejar_for_multidex.
- nocopts now also filter copts
- The Build Event Service (BES) client now properly supports
Google Applicaton Default Credentials. - update dexing tools to Android SDK 26.0.1
- Bazel Android support now requires build-tools 26.0.1 or later.
- Fix a bug in the remote_worker that would at times make it crash on Linux. See #3356
- The java_proto_library rule now supports generated sources. See #2265
Notice: Bazel installers contain binaries licensed under the GPLv2 with
Classpath exception. Those installers should always be redistributed along with
the source code.
Some versions of Bazel contain a bundled version of OpenJDK. The license of the
bundled OpenJDK and other open-source components can be displayed by running
the command bazel license
. The vendor and version information of the bundled
OpenJDK can be displayed by running the command bazel info java-runtime
.
The binaries and source-code of the bundled OpenJDK can be
downloaded from our mirror server.
Security: All our binaries are signed with our
public key 48457EE0.