Google Git
Sign in
bazel / rules_cc / 85221b195f054e874176a7fbd2cc00d04581c633
commit85221b195f054e874176a7fbd2cc00d04581c633[log] [tgz]
authorYun Peng <pcloudy@google.com>Fri Jul 11 07:41:22 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Jul 11 07:41:49 2025 -0700
tree65019e2c6082877c792be9251f898f5276495252
parent0692005a7e02198ec20837affb0fea14db6d3235 [diff]
Support shorten_virtual_includes

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

BEGIN_PUBLIC
Support shorten_virtual_includes (#438)

Context: https://github.com/bazelbuild/bazel/pull/26528, https://github.com/protocolbuffers/protobuf/issues/20085

Enable `shorten_virtual_includes` for MSVC toolchains to shorten virtual include paths to mitigate long path issue on windows.

Closes #438
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/438 from meteorcloudy:shorten_virtual_includes 5ab4b9465c725a59b13d5ebaa69cafdb6006dac1
PiperOrigin-RevId: 781977791
Change-Id: Ia683103cb9da2eed8cca165ccf1243f3ee1357da
2 files changed
tree: 65019e2c6082877c792be9251f898f5276495252
  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: