Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 7a67e9887bb100977408de99a797145062f2e7ca
commit7a67e9887bb100977408de99a797145062f2e7ca[log] [tgz]
authorIvo List <ilist@google.com>Wed Sep 11 05:56:07 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Sep 11 05:56:57 2024 -0700
tree2ced937856422c66c9b2ccf3372eb5ded0dbab31
parent96ac608d348b73a58c5735733f68bd4e660206d4 [diff]
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/238

BEGIN_PUBLIC
Copybara import of the project:

--
2803a12428e6493e48176f46f352a3e78820e7da by Ivo List <ilist@google.com>:

Prepare for release 0.0.10-rc2

--
3423c7320893a84a5166aa9962ce57c3715c4660 by Ivo List <ilist@google.com>:

Format WORKSPACE

--
a99403a6b0ee72aea634b84b3caa065a9290a6fb by Ivo List <ilist@google.com>:

Touch module

--
258d8c9f2410796715cb8fe8a07e2dacf9b217e0 by Ivo List <ilist@google.com>:

Revert "Touch module"

This reverts commit a99403a6b0ee72aea634b84b3caa065a9290a6fb.

END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/238 from comius:release-0.0.10-rc2 258d8c9f2410796715cb8fe8a07e2dacf9b217e0
PiperOrigin-RevId: 673358956
Change-Id: Iabc9c29e6f168cfdfd2f0657438b71654f470cc9
2 files changed
tree: 2ced937856422c66c9b2ccf3372eb5ded0dbab31
  1. .bazelci/
  2. .bcr/
  3. cc/
  4. examples/
  5. tests/
  6. third_party/
  7. tools/
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CODEOWNERS
  12. CONTRIBUTING.md
  13. ISSUE_TEMPLATE.md
  14. LICENSE
  15. MODULE.bazel
  16. README.md
  17. renovate.json
  18. 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: