Google Git
Sign in
bazel / rules_cc / 8169fdde3b47e43213179f45188900877dd153ad
commit8169fdde3b47e43213179f45188900877dd153ad[log] [tgz]
authorUebelAndre <github@uebelandre.com>Wed Aug 27 00:30:32 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Aug 27 00:31:00 2025 -0700
tree01eb07340ed4e927dd9287b6a91323043b218bc1
parente8327fae710a12845a28794ed97ddd6d85c46fdb [diff]
Update cc_wrapper templates to posix shell.

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

BEGIN_PUBLIC
Update cc_wrapper templates to posix shell. (#466)

This updates cc_wrapper templates to use [POSIX sh](https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html) compared to [bash](https://en.wikipedia.org/wiki/Bash_(Unix_shell)) to avoid some reliance on the ability to locate `bash` on `PATH`.

Closes #466
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/466 from UebelAndre:posix 5f655475e956af645508076e3906385dfd414a11
PiperOrigin-RevId: 799906333
Change-Id: I05d8570d8c6ff64e16614dbf58464758c5764ff7
2 files changed
tree: 01eb07340ed4e927dd9287b6a91323043b218bc1
  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: