| commit | c93d01dee9102a64b43b4fc1f24c05fe3a5f4a37 | [log] [tgz] |
|---|---|---|
| author | Mark Reuter <13319190+reutermj@users.noreply.github.com> | Tue Jul 08 19:44:28 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 08 19:45:15 2025 -0700 |
| tree | f15bb7e74e3bd4e0e32d2479db0d1b22959789ee | |
| parent | bdd93e82a0bf2a9f9f9a221cbb9136fe325e95b6 [diff] |
Enable formatting of environment variables in cc_args Copybara Import from https://github.com/bazelbuild/rules_cc/pull/413 BEGIN_PUBLIC Enable formatting of environment variables in cc_args (#413) Windows does not follow the Unix sysroot convention. Instead, it uses the `INCLUDE` and `LIB` environment variables to specify the include and library search paths. This change enables formatting of the values of envirnoment variables set in the `env` attribute of `cc_args` using the standard `format` attribute. This allows Windows users to download a hermetic "sysroot" as part of the build, and set the relevant "INCLUDE" and "LIB" environment variables. Example usage: ``` cc_args( name = "arg-include", actions = [ "@rules_cc//cc/toolchains/actions:c_compile", "@rules_cc//cc/toolchains/actions:cpp_compile_actions", ], env = { "INCLUDE": "{include}", }, format = { "include": ":sysroot-include", }, data = [ ":sysroot-include", ], ) ``` example repo: https://github.com/reutermj/windows-rules-based-toolchain-example Future work: Current implementation for the format substitution only allows for a single variable to be substituted. Users of the API often will need to substitute in multiple paths into the `INCLUDE`/`LIB` environment variables. Closes #413 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/413 from reutermj:main 4c59d66168ca57725051d2044a2949fb5fd7f0c3 PiperOrigin-RevId: 780817009 Change-Id: Ifab4889f94f788f24a2e585d124444b49102839b
This repository contains a Starlark implementation of C++ rules in Bazel.
The rules are being incrementally converted from their native implementations in the Bazel source tree.
For the list of C++ rules, see the Bazel documentation.
Add the following to your WORKSPACE file:
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive") http_archive( name = "rules_cc", urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"], sha256 = "...", )
Then, in your BUILD files, import and use the rules:
load("@rules_cc//cc:defs.bzl", "cc_library") cc_library( ... )
This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.
There are third-party contributed hermetic toolchains you may want to investigate:
If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:
load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains") rules_cc_dependencies() rules_cc_toolchains()
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).
TLDR:
bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \ --input=my_toolchain/CROSSTOOL \ --inline
Bazel and rules_cc are the work of many contributors. We appreciate your help!
To contribute, please read the contribution guidelines: CONTRIBUTING.md.
Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see:
rules_cc mailing list#cc on slack.bazel.build