Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/1fd961973e1c3ea005cb16cbfa1f017258c50f8a
commit
1fd961973e1c3ea005cb16cbfa1f017258c50f8a
[log] [tgz]
author
Fabian Meumertzheim <fabian@meumertzhe.im>
Wed Jan 28 07:40:16 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Jan 28 07:40:42 2026 -0800
tree
4eaf46743c3b938c0cc0d94126d5330e7b63836c
parent
9ed36090ba16d5456790573610771cfb7b3ff8f2 [diff]
Move providers out of native.bzl

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

BEGIN_PUBLIC
Move providers out of native.bzl (#570)

This is necessary to make referencing these symbols a descriptive error in Bazel with autoload disabled. Native `cc_common` is still used by rules_cc and must not fail in the same way.

Work towards https://github.com/bazelbuild/bazel/issues/27684
Related to https://github.com/bazelbuild/bazel/pull/28360

Closes #570
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/570 from fmeum:split-native 9c5f5b2462edfed9ddba0290337cef9a36e5929c
PiperOrigin-RevId: 862230508
Change-Id: I6a3c131f2adc78bb6969b5c959342795dd5d2591
15 files changed
tree: 4eaf46743c3b938c0cc0d94126d5330e7b63836c
  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: