Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 083ace4f11f050677cabad63c735d79f22abdb25
commit083ace4f11f050677cabad63c735d79f22abdb25[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Tue Oct 01 08:32:55 2024 +0200
committerYun Peng <pcloudy@google.com>Fri Oct 04 15:07:57 2024 +0200
treed1e9e3c3b751a44bbff79f4acc76163bf173dbcf
parent7343c660a406e367865d2107255c69bb05f52163 [diff]
Make stardoc a dev dependency

Otherwise rules_cc is transitively incompatible with Bazel 6 through the chain stardoc 0.7.0 -> rules_java 7.6.1.

`stardoc` targets are not needed by consumers of the ruleset.
5 files changed
tree: d1e9e3c3b751a44bbff79f4acc76163bf173dbcf
  1. .bazelci/
  2. .bcr/
  3. cc/
  4. docs/
  5. examples/
  6. tests/
  7. third_party/
  8. tools/
  9. .gitignore
  10. AUTHORS
  11. BUILD
  12. CODEOWNERS
  13. CONTRIBUTING.md
  14. ISSUE_TEMPLATE.md
  15. LICENSE
  16. MODULE.bazel
  17. README.md
  18. renovate.json
  19. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags 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

There is no need to use rules from this repository just yet. If you want to use rules_cc anyway, 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: