Google Git
Sign in
bazel / rules_cc / refs/heads/main
commite3a884c864540b8a93fe906add87b21aab1004f4[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Tue Dec 23 11:16:26 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Tue Dec 23 11:16:56 2025 -0800
tree9fe8ab2e0f454dd5be358a447ec5b12ee1729e68
parent350c70a6e8e76c8b448af6ea23014d06a4ef0fa1 [diff]
Use feature instead of cpp fragment for dSYM generation

This was discussed in https://github.com/bazelbuild/bazel/pull/25881
where we believed it was equivalent. This isn't equivalent if the
toolchain does not support dSYM generations but --apple_generate_dsym is
still passed (as is possible on Linux). In this case we let feature
configuration handle this instead, as this feature is requested when
--apple_generate_dsym is passed. In that case because of this mismatch
this directory will be created "successfully" but it will always be
empty (this would be a failure if it wasn't a tree artifact)

Closes #26925.

PiperOrigin-RevId: 848240203
Change-Id: I7de21ba82fda794ffecb2ad86d2010e46732316f
1 file changed
tree: 9fe8ab2e0f454dd5be358a447ec5b12ee1729e68
  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: