Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/d9d7798dc01deefa4ea8d9e8032a474d10e5df2c
commit
d9d7798dc01deefa4ea8d9e8032a474d10e5df2c
[log] [tgz]
author
Keith Smiley <keithbsmiley@gmail.com>
Mon Mar 16 02:53:56 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Mon Mar 16 02:54:17 2026 -0700
tree
5a8165597b4b85eb813c554ccf43d1f0adb59b8d
parent
748fbdfc8c81e2a7d9c24e2d65cfc16d13398391 [diff]
Add strip_include_prefix textual_hdrs test

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

BEGIN_PUBLIC
Add strip_include_prefix textual_hdrs test (#634)

This is a test case for 1212a51b1324b944b4e9bad60011ba37af57d817 that
didn't merge with that PR because of the tests living in bazel vs here.

Closes #634
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/634 from keith:ks/add-strip_include_prefix-textual_hdrs-test 81a12a5b2a5239ce7822c078bba1bee5ea43442b
PiperOrigin-RevId: 884321378
Change-Id: Ia914af93349ad9c1a152de3f68dfe51eff5f7c7c
5 files changed
tree: 5a8165597b4b85eb813c554ccf43d1f0adb59b8d
  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: