Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 8395ec0172270f3bf92cd7b06c9b5b3f1f679e88
commit8395ec0172270f3bf92cd7b06c9b5b3f1f679e88[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Tue Nov 19 02:58:15 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Tue Nov 19 02:58:45 2024 -0800
tree0529447a55879d29ab73ed4b710f79c030397d0a
parent4db02b76c91137ff930f3b94eb51ae36541b7aec [diff]
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/263

BEGIN_PUBLIC
Copybara import of the project:

--
82e44f3c472981bd13e86074c9ebd82974280030 by Fabian Meumertzheim <fabian@meumertzhe.im>:

Copy over runfiles library from Bazel

The runfiles library can be maintained independently of Bazel releases and bazel_tools can refer to it via an alias.

--
885d333d5565b210c1abc120eeee8e84c14e186f by Fabian Meumertzheim <fabian@meumertzhe.im>:

Switch to new include path and namespace

--
b8cd815963ecb00c826eed56461fd01d771306a1 by Fabian Meumertzheim <fabian@meumertzhe.im>:

Fix CI

--
41b7d48ed80d396c0e98b039a6a078366f21f9dc by Fabian Meumertzheim <fabian@meumertzhe.im>:

Silence warnings

--
b97a30e8bbb4eed94f024171289f28f9d78c4862 by Fabian Meumertzheim <fabian@meumertzhe.im>:

Remove per_file_copt

END_PUBLIC

PiperOrigin-RevId: 697942902
Change-Id: I10a6c9baf0464722fca026db99cf572acfd159f1
9 files changed
tree: 0529447a55879d29ab73ed4b710f79c030397d0a
  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
  • 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: