Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/a464a757729135a164f4b37b23b765847def115f
commit
a464a757729135a164f4b37b23b765847def115f
[log] [tgz]
author
Keith Smiley <keithbsmiley@gmail.com>
Tue Feb 17 09:00:52 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Tue Feb 17 09:01:14 2026 -0800
tree
148d9239e5ce7ba0aadf76b740066f1c8e498a21
parent
2e612c7035ff45051f7397da410b7c6ac728fa2d [diff]
Silence warning with parse_headers

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

BEGIN_PUBLIC
Silence warning with parse_headers (#531)

```
clang -xc++-header -fsyntax-only -c foo.h
clang: warning: argument unused during compilation: '-c' [-Wunused-command-line-argument]
```

This just no longer passes the `-c` to the header parsing action

Closes #531
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/531 from keith:ks/silence-warning-with-parse_headers 688f24d0170352b2b87d75ca73f205ca9cbff5d2
PiperOrigin-RevId: 871344421
Change-Id: Ibf34aad2280abd3229904d922affc49a2c47eac0
1 file changed
tree: 148d9239e5ce7ba0aadf76b740066f1c8e498a21
  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: