Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/541eda5d72e9b5f18e6a24e8d14975afcd865717
commit
541eda5d72e9b5f18e6a24e8d14975afcd865717
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Wed Feb 18 01:57:12 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Feb 18 01:57:40 2026 -0800
tree
606196dc8d528cdde31e950ee19e24ee75130218
parent
ae1df74a5b6ff1530daffe4c2e1218173addc121 [diff]
Only pass profile-correction flag on GCC

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/580
cloned from unknown commit to add BtrGuardian exclusion

BEGIN_PUBLIC
Only pass profile-correction flag on GCC (#580)

This is a GCC flag, Clang emits a warning and ignores it.

Closes #580
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/580 from dzbarsky:zbarsky/profile-correction 7970c980a7c195656fa206e0efe5760e9134910e
PiperOrigin-RevId: 871744266
Change-Id: I7b3664d7f6f0673327cf4be05b11d28ec1b9a9dc
5 files changed
tree: 606196dc8d528cdde31e950ee19e24ee75130218
  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: