Google Git
Sign in
bazel / rules_cc / 1f84d1e945426a7e5aa6ee36476a6a4c4c3a6888
commit1f84d1e945426a7e5aa6ee36476a6a4c4c3a6888[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Wed Sep 24 06:52:59 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Sep 24 06:53:43 2025 -0700
treee78d184a161c2acec6bfc9ebbaf331823624571c
parent74ad1708c9a7e83657b0107bdb9ae535b70fd3f1 [diff]
Fix repo mapping lookup in runfiles library

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

BEGIN_PUBLIC
Fix repo mapping lookup in runfiles library (#494)

The lookup of a prefix match in the repo mapping has to use "floor" semantics (largest element less or equal) and needs to check for bounds to avoid undefined behavior.

Closes #494
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/494 from fmeum:fix-msan-error ed21f4f75f5c6e240021c67a731118888b9a02c4
PiperOrigin-RevId: 810864188
Change-Id: I79d7b959e7e0e30c98cea8e87ec2d97236ae0eae
1 file changed
tree: e78d184a161c2acec6bfc9ebbaf331823624571c
  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: