Google Git
Sign in
bazel / rules_cc / 0b3cceb4d701f87397f2360627c1fcaecd7c6267
commit0b3cceb4d701f87397f2360627c1fcaecd7c6267[log] [tgz]
authorPikachuHy <pikachuhy@linux.alibaba.com>Thu Oct 02 06:14:16 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Oct 02 06:14:56 2025 -0700
tree55592d11cb427ca77452f43aaa5216c71bb1ec90
parentf44b58ba5646809a1fde516e3bea891aa44c4cc5 [diff]
Fix generate_modmap: use default generate_modmap

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

BEGIN_PUBLIC
Fix generate_modmap: use default generate_modmap (#496)

We previously expose generate_modmap attribute in https://github.com/bazelbuild/bazel/commit/8028655414a189b6897b1b51e3e43b5711e0af98 to support https://github.com/bazelbuild/rules_cc/pull/447 . After migrating to the Starlark implementation, this attribute is no longer needed. Remove the override and rely on the default generate_modmap behavior.

Closes #496
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/496 from PikachuHyA:fix_genmodmap 567c1234dc49634311ff512fe8cea73b620030a8
PiperOrigin-RevId: 814203331
Change-Id: Ie1d5100a44df2c4251e856ccfa16d378441a2d7b
1 file changed
tree: 55592d11cb427ca77452f43aaa5216c71bb1ec90
  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: