Google Git
Sign in
bazel / rules_cc / e12b46e3af997b0caa37b53636860ca50fc89e19
commite12b46e3af997b0caa37b53636860ca50fc89e19[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Mon Sep 08 14:21:38 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Sep 08 14:22:16 2025 -0700
tree95a76fd682a71fc867aced0264e86bd52885ad1a
parent5defd67a818940c01993367b1b67038e7b6b277c [diff]
Support eventual removal of do_not_use_macos_set_install_name

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

BEGIN_PUBLIC
Support eventual removal of do_not_use_macos_set_install_name (#379)

https://github.com/bazelbuild/bazel/pull/25682

Closes #379
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/379 from keith:ks/support-eventual-removal-of-do_not_use_macos_set_install_name a5a66384cca02151907e65b81d0c372f4675d71b
PiperOrigin-RevId: 804585431
Change-Id: I9c2ddb82de4fa41cea34443e819f71de06073da0
1 file changed
tree: 95a76fd682a71fc867aced0264e86bd52885ad1a
  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: