Baseline: ac880418885061d1039ad6b3d8c28949782e02d6
Cherry picks:
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.
The --incompatible_expand_directories flag will automatically expand directories in command lines. Design doc: https://docs.google.com/document/d/11agWFiOUiz2htBLj6swPTob5z78TrCxm8DQE4uJLOwM
The --loading_phase_threads flag now defaults to auto (not 200, as was previously the case), 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.
--compilation_mode=dbg that target Android ARM architectures by adding the -g flag.Added --incompatible_disable_legacy_flags_cc_toolchain_api to deprecate legacy cc_toolchain Starlark API for legacy CROSSTOOL fields. Tracking issue is #6434. Migration docs are on the bazel website.
Runfiles in cc_test: the C++ runfiles library (@bazel_tools//tools/cpp/runfiles) can now create Runfiles objects for tests. See //tools/cpp/runfiles/runfiles_src.h (in the Bazel source tree) for documentation.
:cc_binary link action no longer hardcodes -static-libgcc for toolchains that support embedded runtimes (guarded by --experimental_dont_emit_static_libgcc temporarily).
The flag --experimental_enable_cc_configuration_make_variables is removed, use --incompatible_disable_cc_configuration_make_variables instead.
--javabase flag is unset, Bazel locates a JDK using the JAVA_HOME environment variable and searching the PATH. If no JDK is found --javabase will be empty, and builds targeting Java will not be supported. Previously Bazel would fall back to using the embedded JDK as a --javabase, but this is no longer default behaviour. A JDK should be explicitly installed instead to enable Java development.LcovMerger was renamed to CoverageOutputGenerator.
Faster coverage collection for gcc compiled C++ code can now be tested by enabling it with --experimental_cc_coverage.
Add --apple_compiler and --apple_grte_top options. These provide the equivalent of --compiler / --grte_top for the toolchain configured in --apple_crosstool_top.
There is now a same_pkg_direct_rdeps query function. See the query documentation for more details.
Propagating remote errors to the user even if --verbose_failures=false is set.
Add number of configured targets to analysis phase status output.
Bazel will now check stderr instead of stdout to decide if it is outputting to a terminal. --isatty is deprecated, use --is_stderr_atty instead.
--incompatible_disable_late_bound_option_defaults: #6384--incompatible_disable_depset_in_cc_user_flags: #6383--incompatible_disable_cc_toolchain_label_from_crosstool_proto: #6382--incompatible_disable_cc_configuration_make_variables: #6381--incompatible_disable_legacy_cpp_toolchain_skylark_api: #6380incompatible_disable_legacy_flags_cc_toolchain_api: #6434--incompatible_remove_native_git_repository and --incompatible_remove_native_http_archive will be turned on.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!
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.