Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/1212a51b1324b944b4e9bad60011ba37af57d817
commit
1212a51b1324b944b4e9bad60011ba37af57d817
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Wed Jan 21 08:57:21 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Jan 21 08:58:10 2026 -0800
tree
52f3f00f0da89b712c17a42ead3c0c005980b014
parent
e6d30a5681b7d1916b9a6e36cb3d8798d7a9d4c1 [diff]
Make strip_include_prefix apply to textual_hdrs

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

BEGIN_PUBLIC
Make strip_include_prefix apply to textual_hdrs (#537)

Mirror of https://github.com/bazelbuild/bazel/pull/26327

Closes #537
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/537 from keith:ks/make-strip_include_prefix-apply-to-textual_hdrs 72348e45d2e098d9e4f368897754e86c98af1fb8
PiperOrigin-RevId: 859124025
Change-Id: I5425de1829802ee03b8d8a793bea83998ae5aebd
2 files changed
tree: 52f3f00f0da89b712c17a42ead3c0c005980b014
  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. googletest.patch
  16. ISSUE_TEMPLATE.md
  17. LICENSE
  18. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit 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

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: