Sunset C++ toolchain legacy features #22005
Labels
P3
We're not considering working on this, but happy to review a PR. (No assignee)
team-Documentation
Documentation improvements that cannot be directly linked to other team labels
team-Rules-CPP
Issues for C++ rules
type: feature request
From https://bazel.build/versions/6.2.0/docs/cc-toolchain-config-reference#legacy-features-patching-logic:
Most of the legacy features are migrated to Starlark. We should consider sunsetting these legacy features when possible.
The pain point with legacy features is that it's sometime a mystery which features are enabled.
For example,
sysroot
is enabled in Starlark and Java (bazel). If we implement a custom C++ toolchain using unix_cc_toolchain_config.bzl as an example, removingsysroot
feature will still result in--sysroot
flag in compiler flags which is a bit surprising.The text was updated successfully, but these errors were encountered: