Google Git
Sign in
bazel/rules_cc/refs/heads/main
commit
5751961055f4ce39671faa316752866cf0c1d78a
[log]
author
Brad Spencer <brad.spencer@arcticwolf.com>
Tue Jun 09 03:00:50 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Jun 09 03:01:12 2026 -0700
tree
dc5d6d232067be997f629c0a21a5917f98ecc79b
parent
ca4ef233756db4509a771a3c99c4b3ac5854df81 [diff]
MSVC `determinism` feature should use `/Brepro` with linking

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

BEGIN_PUBLIC
MSVC `determinism` feature should use `/Brepro` with linking (#713)

The `/Brepro` (undocumented) argument to MSVC applies to both the compiler and the linker.

The recent commit 94bda81 in #408 fixed determinism with MSVC by passing the argument to the compiler, but not the linker.

Since the flag is undocumented, it is not clear whether it makes a difference when linking MSVC-compiled objects that were themselves compiled with `/Brepro`, but passing it to the linker helps ensure that it is applies in all cases, such as when linker is used with objects built from other languages.

This change adds `all_link_actions` to the list of actions that get the argument.

See https://github.com/llvm/llvm-project/issues/37777 for some of the scant documentation that`lld-link` (and thus real `link.exe`) accepts this option.

Closes #713
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/713 from b-spencer:patch-1 7eb345bd9c4e306b4ae3bc6203296be6de117409
PiperOrigin-RevId: 929075474
Change-Id: I823121cfc649b8b359004f91523483d1a7d2fd40
1 file changed
tree: dc5d6d232067be997f629c0a21a5917f98ecc79b
  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. renovate.json
  22. WORKSPACE
  23. 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: