Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / refs/heads/upstream/main
commit6dd2ef1fefbca004da449578c00d8ffb91a459ca[log] [tgz]
authorAustin Schuh <austin.linux@gmail.com>Fri Jan 09 23:10:48 2026 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Jan 09 23:11:27 2026 -0800
tree40d221a34d22dd393e8a8e3b24f56bfac2a53827
parent67f55bd8e555c0e4e99dde940f1bb29144f371fc [diff]
Register both windows compilers to enable cross compilation

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

BEGIN_PUBLIC
Register both windows compilers to enable cross compilation (#432)

There is a perfectly good cross compiler for the other Windows variant (arm64 vs x86).  The only problem is that it doesn't get registered by default, so it isn't easily available.  Register both of them and let toolchain selection pick the right one automatically.

Closes #432
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/432 from AustinSchuh:windows_cross_compile a738de7a8843f6f48f71092f522c1048d56e08a6
PiperOrigin-RevId: 854483022
Change-Id: Ie366916d725b7e140665686f52f22eeee18a7614
2 files changed
tree: 40d221a34d22dd393e8a8e3b24f56bfac2a53827
  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: