Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 9c23bc9e2c89ce8e70145174e7a351515f7f52c7
commit9c23bc9e2c89ce8e70145174e7a351515f7f52c7[log] [tgz]
authorIvo List <ilist@google.com>Tue Aug 05 02:36:47 2025 -0700
committerIvo List <ilist@google.com>Fri Aug 29 11:29:05 2025 +0200
treee5da844d5f19bc759863dc4519c1b7f6c7f8b619
parentcbee84ad7f583049823f3d1497aab1264cf94f26 [diff]
Remove dependency on protobuf

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

BEGIN_PUBLIC
Remove dependency on protobuf (#449)

This is a new attempt, which is slightly softer than before. It only fails on Bazel8 and later, because it uses native cc_proto_library, so that it doesn't need to depend on the protobuf repository.

Closes #449
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/449 from comius:cc-proto-library-removal-2 655d09580e59802fca299b07f2031b5c960dae65
PiperOrigin-RevId: 791120562
Change-Id: I94e82caf10d08283d4730982b2959058bed4da2d
6 files changed
tree: e5da844d5f19bc759863dc4519c1b7f6c7f8b619
  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

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: