MELLEL 4.0.0 FULL
MELLEL 4.0.0 FOR ANDROID
MELLEL 4.0.0 ANDROID
MELLEL 4.0.0 WINDOWS

C++ rules on Windows calling cc_common.create_linking_context_from_compilation_outputs check whether each target of the rule type should produce a dynamic library.The BAZEL_CURRENT_REPOSITORY preprocessor variable, which holds the canonical name of the Bazel repository containing a cc_* target, is now only set during compilation if the target depends on the C/C++ runfiles library via deps or implementation_deps.Use transition_support.apple_rule_transition from rules_apple instead. Please use cc_toolchain_alias rule instead. The cc_host_toolchain_alias rule is deleted.Enable the feature exclude_bazel_rpaths_in_transitive_libs or use_rpath_instead_of_runpath for those cc_shared_librarys. This might be an incompatible change if you are using RUNPATHs (instead of RPATHs) in your cc_shared_librarys. cc_binary targets with dynamic_deps attributes no longer link indirect dynamic_deps on Unix.Remove 'darwin' as a CPU value, use 'darwin_x86_64' instead.C++ rules use platform-based toolchain resolution ( -incompatible_enable_cc_toolchain_resolution is now on).When this flag is enabled, -features only applies to targets built in the target configuration, and -host_features is used for the host / exec configuration Added a new flag -incompatible_use_host_features.

MELLEL 4.0.0 ANDROID

Set Android Databinding to v2 and Databinding AndroidX to true and remove support for Databinding V1.Android resources will no longer propagate through neverlinked libraries by default.Added support for optimizers rewriting baseline profiles.Dropped support for legacy (pre-D8) desugaring.Updated Android manifest merger to v30.1.3.The flag -android_include_proguard_location_references is removed and -no_proguard_location_reference is now added unconditionally to the command line of aapt2.Refer to #18339 for migration advice.īazel’s embedded JVM has been upgraded to JDK 21. Sharded tests with test runners that do not properly advertise support for test sharding will fail. -incompatible_check_sharding_support is enabled by default.

MELLEL 4.0.0 FULL

Many flags have been removed as part of the effort to remove and clean up unused flags (see the appendix for a full list also #19296).

-incompatible_visibility_private_attributes_at_definition.

-incompatible_always_check_depset_elements.

-incompatible_existing_rules_immutable_view.

-incompatible_enable_cc_toolchain_resolution.

- incompatible_fail_on_unknown_attributes.

- incompatible_disable_objc_library_transition.

- incompatible_config_setting_private_default_visibilityĪlready flipped and will be removed at head:.

- incompatible_disable_starlark_host_transitions.

- incompatible_stop_exporting_language_modules.

- incompatible_disable_target_provider_fields.

- incompatible_disallow_struct_provider_syntax.

-incompatible_disable_non_executable_java_binary.

Prepare for future Bazel changes by using the following incompatible flags for early migration:

This mode also enables Bazel to gracefully handle remote cache evictions.

This reduces the number of downloaded artifacts when using remote caching and execution significantly, speeding up builds by up to 40%.Build without the Bytes (BwoB) is now enabled by default ( -remote_download_outputs now defaults to toplevel).The repository defines four standard Android platforms for projects that use those rules, Full details are available in the Android Platforms announcement. Android projects will need to stop passing the legacy flag -fat_apk_cpu, and instead use -android_platforms using platforms defined with the constraint. Android rules now use platforms and toolchains to control the target devices.

MELLEL 4.0.0 FOR ANDROID

Platform-based toolchain resolution is now enabled for Android and C++.This reduces end-to-end wall time for multi-target builds by up to 15%.Bazel now starts executing actions while it is still analyzing other top-level targets (Project Skymeld).See the Bzlmod migration guide for more information. With Bazel 8, we plan to disable WORKSPACE by default (can still be enabled) and with Bazel 9 we plan to remove the legacy WORKSPACE based dependency system.

With Bazel 7 you can still use WORKSPACE, but you should plan migrating your external dependencies from WORKSPACE to MODULE.bazel.

Bzlmod (Bazel’s new way to manage 3rd party dependencies) is now enabled by default (-enable_bzlmod).

It contains new features and backwards incompatible changes.

Mellel 4.0.0