Google Git
Sign in
bazel / rules_cc / refs/heads/main
commitae0252b004e67428715c565413db51c9e0b17194[log] [tgz]
authorKeith Smiley <keithbsmiley@gmail.com>Wed Nov 26 05:55:58 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Nov 26 05:56:35 2025 -0800
tree6b391c1578245f2ab3e47586d50e352e5719c9b1
parent78bbf2aa0097f9f47f8a93081cff8d90b19be7c0 [diff]
Prefix cxx_builtin_include_directories with %workspace%

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

BEGIN_PUBLIC
Prefix cxx_builtin_include_directories with %workspace% (#536)

When passing a directory as a sysroot, the files in the sysroot must be
added here. Previously just the raw relative path such as
`external/sysroot/` was set, which bazel still errored on with
undeclared inclusions. By prefixing this with `%workspace%` bazel is
happy.

Since we're always passing some bazel target here, this seems safe.

Closes #536
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/536 from keith:ks/prefix-cxx_builtin_include_directories-with-workspace 1f91c4609f5f0ec5d63f5dcf43b673553e500038
PiperOrigin-RevId: 837085143
Change-Id: If6426c020c26a1af51c2d38ca882c954265fb016
1 file changed
tree: 6b391c1578245f2ab3e47586d50e352e5719c9b1
  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: