Google Git
Sign in
fuchsia/third_party/github.com/bazelbuild/rules_cc/0926ec42202e20871b13e8688af20d013d6073f8
commit
0926ec42202e20871b13e8688af20d013d6073f8
[log]
author
Googler <noreply@google.com>
Fri Jul 24 09:44:52 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Jul 24 09:45:21 2026 -0700
tree
9520e1c1c97e0f5fcea106389e75a11cd655989a
parent
bcd0612c5890fd948d278090c164d211617b6c3f [diff]
Migrate batch 2 of CppModulesConfiguredTargetTest to Starlark

Migrated tests:
- testCppModulesCcLibraryConfigurationWithFeatures
- testCppModulesCcBinaryConfigurationWithFeatures
- testCppModulesCcTestConfigurationWithFeatures
- testSameModuleInterfacesFileInCcLibraryTwice
- testSameModuleInterfacesFileInCcBinaryTwice
- testSameModuleInterfacesFileInCcTestTwice

Also:
- Fixed a bug in compile.bzl where needs_include_validation was missing in
  _create_scan_deps_action.
- Fixed a bug in compile.bzl where _create_compile_action did not accept C++
  modules arguments (additional_outputs, module_files, modmap_file,
  modmap_input_file), causing a BazelCI failure when they were passed.
- Configured the mock toolchain with 'c++-module-deps-scanning' and
  'c++20-module-compile' action configs for these tests, fixing BazelCI
  failures.
- Deleted CppModulesConfiguredTargetTest.java and removed its target from BUILD.
PiperOrigin-RevId: 953413765
Change-Id: I169abcc3c6380d64d5436b7796ea77a791dde160
3 files changed
tree: 9520e1c1c97e0f5fcea106389e75a11cd655989a
  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: