Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 28cf2e81608fc3100c0b1534dd783653790d5591
commit28cf2e81608fc3100c0b1534dd783653790d5591[log] [tgz]
authorIvo List <ilist@google.com>Thu Nov 07 05:14:15 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Nov 07 05:14:59 2024 -0800
tree13afb19acdfd3b1e9975173c42b4e24adbaf7b74
parentda65f241058e3a1274a7512a9fcd28cd0f487de6 [diff]
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/269

BEGIN_PUBLIC
Copybara import of the project:

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

Revert "Remove cc_proto_library from defs.bzl"

This reverts commit b15fed2409182bef28c256bcb98a64736409fbec.

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

Move back WORKSPACE.bzlmod (unrevert)

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

Rename protobuf to com_google_protobuf

This keeps compatiblity with WORKSPACE mode in older Bazel versions

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

Adding deprecated comment

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

Restore # @unsorted-dict-items

END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/269 from comius:add-back-cc_proto_library a272300c18437f0f4ca15d0a44760b83f0a99a64
PiperOrigin-RevId: 694079850
Change-Id: Iaa57586636997fd3db9cf9289bddc40c673033c9
3 files changed
tree: 13afb19acdfd3b1e9975173c42b4e24adbaf7b74
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  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
  20. WORKSPACE.bzlmod
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: