Google Git
Sign in
bazel / rules_cc / 0692005a7e02198ec20837affb0fea14db6d3235
commit0692005a7e02198ec20837affb0fea14db6d3235[log] [tgz]
authorPikachuHy <pikachuhy@linux.alibaba.com>Wed Jul 09 09:37:45 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Jul 09 09:38:35 2025 -0700
treeefa271382b7279e18d9a875ba093dd23cb939f9c
parentc93d01dee9102a64b43b4fc1f24c05fe3a5f4a37 [diff]
Add cpp module artifact name pattern

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

BEGIN_PUBLIC
Add cpp module artifact name pattern (#429)

see https://github.com/bazelbuild/bazel/pull/22553#discussion_r2169206515

Closes #429
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/429 from PikachuHyA:artifact_name_pattern edaaf4f226789ef7d3b10775b4370d9e3cc51b93
PiperOrigin-RevId: 781091471
Change-Id: Ic119cf2c87ec55e8e063d358640512c48c3b4667
1 file changed
tree: efa271382b7279e18d9a875ba093dd23cb939f9c
  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: