Google Git
Sign in
bazel / rules_cc / 9dbc37f9c46e4306d59ceb1b114a0810234b984f
commit9dbc37f9c46e4306d59ceb1b114a0810234b984f[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Tue Sep 09 08:15:11 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Tue Sep 09 08:15:58 2025 -0700
tree0790a50313fa5770159ab354a0dbc7dc3be39094
parent2a71690ab12864739ef12d3c2864ab8fb4a6027e [diff]
Add support for `--incompatible_compact_repo_mapping_manifest`

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

BEGIN_PUBLIC
Add support for `--incompatible_compact_repo_mapping_manifest` (#417)

Closes #417
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/417 from fmeum:compact-repo-mapping 09aaf16098a943a7a08f0c2374adc474abd55e31
PiperOrigin-RevId: 804917692
Change-Id: I2399ee18d785cfaba5cbe1d0502bb1a805fe992e
2 files changed
tree: 0790a50313fa5770159ab354a0dbc7dc3be39094
  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: