Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/fad3ad373c833a69d6a6b8d97c5ee53027ff111f
commit
fad3ad373c833a69d6a6b8d97c5ee53027ff111f
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Thu Jul 02 10:58:37 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Thu Jul 02 10:58:59 2026 -0700
tree
52d585eead9a0da1516cef9bc9056cb221492d50
parent
593d6fc644f925da7651590a250bb94d4d91808a [diff]
Starlarkify compute_output_name_prefix_dir

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

BEGIN_PUBLIC
Starlarkify compute_output_name_prefix_dir (#761)

## Summary

Replace both `_cc_internal.compute_output_name_prefix_dir` calls with a private Starlark helper. The helper returns `non_arc` for purposes ending in `_non_objc_arc`, `arc` for purposes ending in `_objc_arc`, and an empty prefix otherwise.

`compile()` normalizes an unset purpose to an empty string before these calls, so the native helper's configuration-mnemonic fallback was not reachable from either rules_cc caller.

Configured-target coverage verifies that Objective-C ARC and non-ARC sources retain separate output directories.

Closes #761
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/761 from dzbarsky:codex/starlarkify-compute-output-name-prefix-dir d06f9d3aa88686a078b8c864cc7afc87ec4b8083
PiperOrigin-RevId: 941761713
Change-Id: I3398d919cf7e4b287813de168b4b80f8373f0d6e
2 files changed
tree: 52d585eead9a0da1516cef9bc9056cb221492d50
  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: