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
12 files changed
tree: 945bfc39eb2b69bf3bc4eb001dace05f4d50c5d0
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. AUTHORS
  11. BUILD
  12. CHANGELOG.md
  13. CODEOWNERS
  14. combine_distfiles.py
  15. combine_distfiles_to_tar.sh
  16. compile.sh
  17. CONTRIBUTING.md
  18. CONTRIBUTORS
  19. distdir.bzl
  20. ISSUE_TEMPLATE.md
  21. LICENSE
  22. README.md
  23. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status

Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.