Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / refs/heads/upstream/main
commitc645f6b19ab45eea21242a29c4a9a10d028d52f0[log] [tgz]
authorSteven Le Rouzic <steven.lerouzic@gmail.com>Thu Sep 25 09:12:04 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Sep 25 09:12:43 2025 -0700
tree6ff1137772737d151b6f75070fe7998f72d381ea
parentaaf476a090bfb537758637b5ca37633e6420aa49 [diff]
Fix absolute file paths checking for Windows

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

BEGIN_PUBLIC
Fix absolute file paths checking for Windows (#477)

This is a fix for #476 and uses `bazel_skylib`'s `is_absolute` function. I looked for other places that would need a similar fix but found only one more, so I may have missed some.

Closes #477
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/477 from stevenlr:fix_absolute_include_paths_check_windows ba54fcece2edbfd2535d39d3e69c81ddf7062f4a
PiperOrigin-RevId: 811375155
Change-Id: Ie1626dd16dd9a100f55ffcadfcfc2eedf93e646b
7 files changed
tree: 6ff1137772737d151b6f75070fe7998f72d381ea
  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: