Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/6cc1bf04ed7a89e39788cea1e10738136c9dd082
commit
6cc1bf04ed7a89e39788cea1e10738136c9dd082
[log]
author
Fabian Meumertzheim <fabian@meumertzhe.im>
Thu Aug 13 02:22:03 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Thu Aug 13 02:22:47 2026 -0700
tree
faf1422726b040c2ba8da3bd0b39767e69ce6380
parent
0e3cf8f552740a1ed84b0f8a0fd739b4bcf7ba53 [diff]
Expand tree artifacts in textual_hdrs in generated module maps (#787)

Tree artifacts in a `cc_library`'s `textual_hdrs` end up in the generated module map as a single `header` entry with the directory's path, which fails to parse (`error: header '<dir path>' not found`), instead of one `textual header` entry per contained file. `hdrs` and `srcs` already expand tree artifacts via the module map action's tree expander; this applies the same expansion to the `public_textual_headers` bucket.

Closes #787

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/787 from fmeum:textual-hdrs-tree-expansion 83f1cf1cb41fce63c6a5c712fe5ba0d610a33036
PiperOrigin-RevId: 963952603
Change-Id: If193b253b0343583c283e3027e5154282afe8139
1 file changed
tree: faf1422726b040c2ba8da3bd0b39767e69ce6380
  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. local_bazel.bzl
  19. MODULE.bazel
  20. README.md
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains C, C++, and Objective-C language support for the Bazel build system.

For this module's main reference, see the Bazel documentation.

Get Started

Install Bazel

Follow the official instructions to Install Bazel.

Add rules_cc to your MODULE.bazel

Add the latest release to your MODULE.bazel project file.

Declare a build target

In a BUILD.bazel file, import and use the rules:

load("@rules_cc//cc:cc_binary.bzl", "cc_binary")

cc_binary(
    name = "hello_world",
    srcs = ["hello_world.cc"],
)

Build and run your project

Build and run your C/C++ binary with one command:

$ bazel run hello_world

To build the project without running the binary, use Bazel's build subcommand:

$ bazel build hello_world

Toolchains

Default autoconfigured toolchain

rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.

You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:

--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

Hermetic toolchains

Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:

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: