The Bazel team is happy to announce a new version of Bazel, Bazel 0.19.
This document lists the major changes since Bazel 0.18.
--loading_phase_threadsflag now defaults to
autoinstead of 200, which at the moment corresponds to the number of CPUs. This is appropriate for most users. However, if your sources reside on a network file system, increasing this value may yield better analysis-time performance when disk caches are cold.
- Fixed missing debug symbols when building native code with
--compilation_mode=dbgthat target Android ARM architectures by adding the
cc_test: the C++ runfiles library (
@bazel_tools//tools/cpp/runfiles) can now create Runfiles objects for tests. See
//tools/cpp/runfiles/runfiles_src.hin the Bazel source tree for documentation.
:cc_binarylink action no longer hardcodes
-static-libgccfor toolchains that support embedded runtimes (guarded by
--experimental_enable_cc_configuration_make_variablesis removed, use
- Bazel now requires a JDK to be installed as it no longer falls back to the internal JDK if the
--javabaseflag is not set. Instead, Bazel now searches for a JDK within the
PATHenvironment variables. If Bazel cannot find a JDK, it will not be able to run Java builds.
- LcovMerger was renamed to CoverageOutputGenerator. Please use
instead of the previous
- You can now enable a new coverage method for C++ rules that use gcc with the
--experimental_cc_coverageflag. The flag will use gcov instead of lcov to collect coverage information. This new implementation fixes some of the C++ coverage correctness issues ( respecting
--instrument_test_targetsflags ). There have been observed faster clean and incremental times when invoking bazel coverage ( small overhead compared to test runtimes instead of 2x test runtime ), but more measurements need to be done.
--apple_grte_top options. These provide the equivalent of
--grte_topfor the toolchain configured in
There is now a
Bazel now propagates remote errors to the user even if
The number of configured targets is now shown in the analysis phase status output.
Bazel will now check stderr instead of stdout to decide if it is outputting to a terminal.
--isattyis deprecated, use
We will do incompatible changes in Bazel 0.20. We encourage you to migrate in advance (or report any migration difficulty) with the following flags:
Thank you to our contributors!
This release contains contributions from many people at Google, as well as Andreas Herrmann, Andreas Hippler, Benjamin Peterson, David Ostrovsky, Ed Baunton, George Gensure, Igal Tabachnik, Jason Gavris, Loo Rong Jie, rmalik, and Yannic Bonenberger
Thank you to everyone who contributed to this release!