| commit | c7e5c8c9b6a53695b29766f7fcfe655ef2609b1d | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Mon Jul 14 14:40:42 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 14 14:41:18 2025 -0700 |
| tree | e60fcc28de02d4751c1bd34bb2f0bf5b0b3e9d74 | |
| parent | b77476aade9b7424bc53880fddf99874e42e4634 [diff] |
Enable `/std:c++17` by default for the Windows cc toolchain Copybara Import from https://github.com/bazelbuild/rules_cc/pull/440 BEGIN_PUBLIC Enable `/std:c++17` by default for the Windows cc toolchain (#440) Context: https://github.com/bazelbuild/bazel/issues/26523#issuecomment-3062496169 Closes #440 END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/440 from bazelbuild:meteorcloudy-patch-6 22a0f1ac48fcb5bf32e1453b52c285ff7bff0049 PiperOrigin-RevId: 783048271 Change-Id: I4b7f9092a41d3af956d78ed4f4324104c30c0b2d
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.
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( ... )
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()
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
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
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:
rules_cc mailing list#cc on slack.bazel.build