Note: This section is intended for Bazel developers, and is not needed by rule authors.
Several SkyFunction classes implement the toolchain resolution process:
SingleToolchainResolutionFunctionresolves a single toolchain type for every execution platform. That is, for every execution platform it finds the best registered toolchain to use based on the following criteria:
- Make sure the toolchain and target platform are compatible, by checking
- Make sure the toolchain and execution platform are compatible, by
- If multiple toolchains are left, choose the highest-priority one (the one that was registered first).
- Make sure the toolchain and target platform are compatible, by checking the
SingleToolchainResolutionFunctionfor each requested toolchain type, and then determines the best execution platform to use.
- First, remove any execution platform that does not have a valid toolchain for each requested toolchain type.
- If multiple execution platforms are left, choose the highest-priority
one (the one that was registered first).
- If the execution platform is already set by the toolchain transition, it will be selected first as described below.
As discussed in Toolchains and Configurations,
the dependency from a target to a toolchain uses a special configuration that
forces the execution platform to be the same for both. Despite the name
"toolchain transition", this is not implemented as a configuration
transition, but instead as a special subclass of
In addition to the other data in
ConfiguredTargetKey, this subclass also holds
the label of the execution platform. When
considering which execution platform to use, if the forced execution platform
ToolchainDependencyConfiguredTargetKey is valid, it will be used even
if it is not the highest-priority.
Note: If the forced execution platform is not valid (because there are no valid toolchains, or because of execution constraints from the rule or target), then the highest-priority valid execution platform will be used instead.