When creating a rule-based toolchain, legacy features must be explicitly enabled in order for tool invocations to be correctly constructed. This can be done in one of two ways:
This is a bit of a stumbling block, since it's not exactly obvious which of these legacy features are required to construct a working toolchain, or how to re-implement these features correctly in a way that makes Bazel happy.
There's a few potential paths to pursue here:
1. Have an option on `cc_toolchain` that enables all legacy features.
2. Provide features (or better, raw `cc_args `/`cc_args_list`) that implement the required flags, and either provide guidance on how to comprehensively build a toolchain that includes the required arguments or make the toolchain rules infer the required args if no args are explicitly provided.
When creating a rule-based toolchain, legacy features must be explicitly enabled in order for tool invocations to be correctly constructed. This can be done in one of two ways:
implies
on acc_action_type_config
:cc_toolchain
.cc_toolchain( name = "my_toolchain",
...
)