Google GitGoogle Git
Sign in
fuchsia/third_party/github.com/bazelbuild/rules_cc/9b9b7decbb1be6fee6af60a7d1972ae96108a326
commit
9b9b7decbb1be6fee6af60a7d1972ae96108a326
[log]
author
Fabian Meumertzheim <fabian@meumertzhe.im>
Fri Oct 09 15:53:24 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Oct 09 15:54:00 2026 -0700
tree
9f41c362913e73e3d61e10d6ba66945a0d968bfd
parent
f96573d6e51487f8c313cd57bd498fe328a5a6ff [diff]
Keep tool paths of generated files relative to the execution root (#901)

`_compute_tool_paths` prefixes every relative tool path with the package of the `cc_toolchain`, which turns exec-cfg paths into non-existent ones. With apple_support 2.8.4, which Bazel@HEAD now bundles and thus selects by default on macOS, `$(CC)` expands to the nonsensical

```
external/apple_support++apple_cc_configure_extension+local_config_apple_cc/bazel-out/darwin_arm64-opt-exec-ST-<hash>/bin/external/apple_support+/crosstool/wrapped_clang
```

instead of

```
bazel-out/darwin_arm64-opt-exec-ST-<hash>/bin/external/apple_support+/crosstool/wrapped_clang
```

This PR keeps tool paths that start with the output directory as they are.

Closes #901

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/901 from fmeum:generated-tool-paths 103fab867e66d382e2461ef5ba91f547e33b64db
PiperOrigin-RevId: 996808000
Change-Id: Ice1f696166553d98f893dd6c430a769f3b9e691e
4 files changed
tree: 9f41c362913e73e3d61e10d6ba66945a0d968bfd
  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. CONTRIBUTING.md
  14. googletest.patch
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. local_bazel.bzl
  18. MODULE.bazel
  19. README.md
  20. WORKSPACE
  21. 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: