Google Git
Sign in
bazel / rules_cc / a0925f28bb4a70857ffdb0b855b9686eb4c0d0aa
commita0925f28bb4a70857ffdb0b855b9686eb4c0d0aa[log] [tgz]
authorMarcel <maleo@google.com>Thu Aug 28 12:12:51 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Aug 28 12:13:26 2025 -0700
tree628eb6fd185c1aac8f71b5b1a1777abbc04822c4
parent8c3abd393a3aace8f07e0d8b923054f14893fbef [diff]
Add instructions for compatibility proxy repo to release notes

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

BEGIN_PUBLIC
Add instructions for compatibility proxy repo to release notes (#475)

This is loaded via `cc_binary.bzl`.

Closes #475
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/475 from mering:release-notes-compatibility-proxy 9a78cfb366c060791fa29365959cde3ad155427e
PiperOrigin-RevId: 800562517
Change-Id: I434a61944f68cc960d3d7ce22647a60fbbb4baf2
1 file changed
tree: 628eb6fd185c1aac8f71b5b1a1777abbc04822c4
  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: