Google Git
Sign in
bazel / rules_cc / bdd93e82a0bf2a9f9f9a221cbb9136fe325e95b6
commitbdd93e82a0bf2a9f9f9a221cbb9136fe325e95b6[log] [tgz]
authorPikachuHy <pikachuhy@linux.alibaba.com>Mon Jul 07 07:00:41 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Jul 07 07:01:20 2025 -0700
tree2a85a00d3b42f0bf1f0dcd0883ce21a2a9217683
parentfe41fc4ea219c9d3680ee536bba6681f3baf838e [diff]
Add DEPS_SCANNER_OUTPUT_FILE env variable for cpp_module_deps_scanning action

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

BEGIN_PUBLIC
Add DEPS_SCANNER_OUTPUT_FILE env variable for cpp_module_deps_scanning action (#428)

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

Closes #428
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/428 from PikachuHyA:env_entry c668abdc059e3c2963784d764ddd181b24cf1397
PiperOrigin-RevId: 780093903
Change-Id: I0762df638e30054ce33e051522f22ad5a89e633f
1 file changed
tree: 2a85a00d3b42f0bf1f0dcd0883ce21a2a9217683
  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: