Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / cbee84ad7f583049823f3d1497aab1264cf94f26
commitcbee84ad7f583049823f3d1497aab1264cf94f26[log] [tgz]
authorYun Peng <pcloudy@google.com>Thu Jul 17 06:10:37 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Jul 17 06:11:35 2025 -0700
treeb0fd919ed585940e9beaf08b26e39d54312d7db8
parentd068b730235538bf1469c90b50b3c99e3c2152ca [diff]
Use a separate feature for cpp std option on Windows

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

BEGIN_PUBLIC
Use a separate feature for cpp std option on Windows (#443)

Address https://github.com/bazelbuild/rules_cc/pull/440#issuecomment-3077629397

We should probably do the same for unix cc toolchains, but that needs more clean up first.

Closes #443
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/443 from meteorcloudy:msvc_cpp_std 3c4f7b33a73bbd4ef78440a88fd07d684aac6ff7
PiperOrigin-RevId: 784153348
Change-Id: Ibc1b580d7b5b6df34ec1db70f2005b9002585f65
3 files changed
tree: b0fd919ed585940e9beaf08b26e39d54312d7db8
  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. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. 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: