Google Git
Sign in
bazel/rules_cc/refs/heads/main
commit
bea7a422995dd6af17d5793d513548432e8815a3
[log] [tgz]
author
Keith Smiley <keithbsmiley@gmail.com>
Wed Mar 04 08:36:40 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Mar 04 08:37:11 2026 -0800
tree
4eae38a2502ac7a34d76ff58b8a5b21ad33c89ab
parent
01a1eced1d61670e3fe1310ccaaa45635aaf90b1 [diff]
Move remote config_setting to rules_cc

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

BEGIN_PUBLIC
Move remote config_setting to rules_cc (#615)

This was removed from bazel in https://github.com/bazelbuild/bazel/commit/e81949554f3ecab5e2c4afd79031f498f36427fe

I think ideally we would drop this but in the meantime this retains
compatibility assuming anything was using this.

Closes #615
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/615 from keith:ks/move-remote-config_setting-to-rules_cc 581de0a18f606d1c58dc643ae06f5f7476e46791
PiperOrigin-RevId: 878507636
Change-Id: I90dd6365901179997e1632f2c887d2c37251fa9b
1 file changed
tree: 4eae38a2502ac7a34d76ff58b8a5b21ad33c89ab
  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: