Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 4a3bc88cee463795ae778defbf52ef092f9f47f9
commit4a3bc88cee463795ae778defbf52ef092f9f47f9[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Fri Jan 31 05:28:31 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Jan 31 05:28:56 2025 -0800
treea570f2f78ae6900e26964ae0a8949b91e457566c
parent82e6354d86dd6e0bee4fe88b75dfe3a6b75a6d8f [diff]
Add preprocessor_defines args and feature

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/337

BEGIN_PUBLIC
Add preprocessor_defines args and feature (#337)

Using the feature allows you to make sure the legacy toolchain feature
is suppressed.

This is the diff in the action config:

```
 flag_set {
+  action: "assemble"
   action: "c++-compile"
   action: "c++-header-parsing"
+  action: "c++-module-codegen"
   action: "c++-module-compile"
   action: "c-compile"
   action: "clif-match"
   action: "linkstamp-compile"
+  action: "lto-backend"
+  action: "objc++-compile"
+  action: "objc-compile"
   action: "preprocess-assemble"
```

I intentionally made this apply to all compile actions since it can
affect them.

Closes #337
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/337 from keith:ks/add-preprocessor_defines-args-and-feature db40edd27302fb528a25ed27617c4e6d501f330c
PiperOrigin-RevId: 721738788
Change-Id: If977770e96352c97f86897ed32d78ad837541175
2 files changed
tree: a570f2f78ae6900e26964ae0a8949b91e457566c
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags Build status

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.

Getting Started

There is no need to use rules from this repository just yet. If you want to use rules_cc anyway, 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(
    ...
)

Using the rules_cc toolchain

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()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

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

Contributing

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: