Google Git
Sign in
bazel / rules_cc / b77476aade9b7424bc53880fddf99874e42e4634
commitb77476aade9b7424bc53880fddf99874e42e4634[log] [tgz]
authorAlexandre Rostovtsev <arostovtsev@google.com>Mon Jul 14 06:07:11 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Jul 14 06:07:49 2025 -0700
tree360e884dafae259138fa45f6703ce16617d43589
parentff06b70246c165fd0ca011e1b6b5a195762c949b [diff]
Fix missing deps in some bzl_library targets

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

BEGIN_PUBLIC
Fix missing deps in some bzl_library targets (#439)

Complete transitive deps of .bzl files are needed for tools like Stardoc.

See https://github.com/bazel-contrib/rules_go/issues/4394

Closes #439
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/439 from tetromino:main 49a761d5b16b4905a2cef8cbb0d0522bdc441d49
PiperOrigin-RevId: 782874155
Change-Id: Ie4995859f8a64eda3c64fd515c41dfc23e6b6cf1
2 files changed
tree: 360e884dafae259138fa45f6703ce16617d43589
  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: