Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make creating a CcToolchainConfigInfo from Skylark possible
Work towards issue #5380. //tools/cpp/cc_toolchain_config_lib.bzl contains all the necessary functionality for one to be able to create a CcToolchainConfigInfo provider from Skylark. CcToolchainConfigInfo currently encapsulates the info read from the CROSSTOOL file. We are moving away from using the CROSSTOOL files, in the future we will reroute the logic through an attribute of cc_toolchain that will point to a Skylark rule. A CcToolchainConfigInfo provider can be created with the cc_common.create_cc_toolchain_config_info() method. e.g: crosstool_rule = rule{ implementation = _impl, provides = [CcToolchainConfigInfo], ) def _impl(ctx): feature1 = feature( name = "feature_one", flag_sets = [ flag_set(actions = ["action1"]), flag_set( actions = ["action1"], flag_groups = [ flag_group( flags = ["flag1"], ), flag_group( flag_groups = [ flag_group( flags = ["flag1"], ), ], expand_if_equal = variable_with_value( name = "variable1", value = "value", ), ), ], expand_if_all_available = ["sysroot"], ), ], ) action_config1 = action_config(action_name = "action_one", enabled = True) action_config2 = action_config( action_name = "action_two", enabled = True, tools = [tool(path = "/a/b/c")], ) artifact_name_pattern1 = artifact_name_pattern( category_name = "static_library", prefix = "prefix", extension = ".a", ) cc_target_os = "os" return cc_common.create_cc_toolchain_config_info( features = [feature1], action_configs = [action_config1, action_config2], artifact_name_patterns = [artifact_name_pattern1], cc_target_os = cc_target_os, make_variables = [make_variable(name = "v1", value = "val")], ) RELNOTES: None. PiperOrigin-RevId: 209648136
- Loading branch information