Overview
Request 648812 accepted
- Update to version 0.19.0:
* The --incompatible_expand_directories flag automatically
expands directories in command lines. See the design document.
* The --loading_phase_threads flag now defaults to auto instead
of 200, which at the moment corresponds to the number of CPUs.
* Fixed missing debug symbols when building native code with
--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. See the instructions for
migration.
* 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.
* Bazel now requires a JDK to be installed as it no longer falls
back to the internal JDK if the --javabase flag is not set.
Instead, Bazel now searches for a JDK within the JAVA_HOME and
PATH environment variables. If Bazel cannot find a JDK, it will
not be able to run Java builds.
* LcovMerger was renamed to CoverageOutputGenerator.
* A new coverage method for C++ rules that uses gcc with the
--experimental_cc_coverage flag. The flag will use gcov
instead of lcov to collect coverage information. This new
implementation fixes some of the C++ coverage correctness
issues ( respecting --instrumentation_filter and
--instrument_test_targets flags ).
* 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.
* 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 now checks stderr instead of stdout to decide if it is
outputting to a terminal. --isatty is deprecated, use
--is_stderr_atty instead.
- enabled aarch64 build and disabled armv7l build as this one fails
due to java memory errors
Request History
mrostecki created request
- Update to version 0.19.0:
* The --incompatible_expand_directories flag automatically
expands directories in command lines. See the design document.
* The --loading_phase_threads flag now defaults to auto instead
of 200, which at the moment corresponds to the number of CPUs.
* Fixed missing debug symbols when building native code with
--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. See the instructions for
migration.
* 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.
* Bazel now requires a JDK to be installed as it no longer falls
back to the internal JDK if the --javabase flag is not set.
Instead, Bazel now searches for a JDK within the JAVA_HOME and
PATH environment variables. If Bazel cannot find a JDK, it will
not be able to run Java builds.
* LcovMerger was renamed to CoverageOutputGenerator.
* A new coverage method for C++ rules that uses gcc with the
--experimental_cc_coverage flag. The flag will use gcov
instead of lcov to collect coverage information. This new
implementation fixes some of the C++ coverage correctness
issues ( respecting --instrumentation_filter and
--instrument_test_targets flags ).
* 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.
* 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 now checks stderr instead of stdout to decide if it is
outputting to a terminal. --isatty is deprecated, use
--is_stderr_atty instead.
- enabled aarch64 build and disabled armv7l build as this one fails
due to java memory errors
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:32"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:32
repo-checker accepted review
cycle and install check passed
dimstar accepted review
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory