Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / be107bfeafc5f5ccb35aae9c709625e026f4c965
commitbe107bfeafc5f5ccb35aae9c709625e026f4c965[log] [tgz]
authorAustin Schuh <austin.linux@gmail.com>Tue Dec 16 06:30:08 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Tue Dec 16 06:30:40 2025 -0800
tree49927594ad243a0f4a993e9fd06edbae79c3a4ce
parent4800b60d7056af7abd0544997c5d3fd4084801d0 [diff]
Make windows toolchain configurable with BAZEL_*OPTS

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

BEGIN_PUBLIC
Make windows toolchain configurable with BAZEL_*OPTS (#431)

This brings the same functionality that exists in Linux to Windows. When cross compiling with transitions, --copts and friends apply to both the host OS, and the target of cross compilation.  This necessitates moving all flags to the toolchain.  There is no way to do this today for the windows toolchains without writing a toolchain from scratch, which isn't ideal for a couple of small flag changes.

While we are here, make `/D_WIN32_WINNT=0x0601` configurable too in the same way.

Closes #431
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/431 from AustinSchuh:configurable_windows_toolchain 96e665ff7fdbb248970e0e6784e4a2a868720221
PiperOrigin-RevId: 845241768
Change-Id: If5f7aa71d6b69c631d77fb2658485d596ae04a1a
4 files changed
tree: 49927594ad243a0f4a993e9fd06edbae79c3a4ce
  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. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

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

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

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: