Google Git
Sign in
bazel / rules_cc / 9e87522bbe29519f43a16edeb254f49ed7b7e224
commit9e87522bbe29519f43a16edeb254f49ed7b7e224[log] [tgz]
authorGoogler <ilist@google.com>Mon Feb 17 09:09:49 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Feb 17 09:10:23 2025 -0800
tree1bc22c2ed4697f31bfc917beecb862f4b1ac7de2
parent9c91c036a100abfc0c1aa54ae30a7214d28686fa [diff]
Automated rollback of commit ba3ec91a5592f749ac3b19d0195fa40089f1bd66.

*** Reason for rollback ***

This seems to be causing failures on Google rules_cc presubmit (the internal one).
https://buildkite.com/bazel/google-rules-cc-presubmit/builds/944#019514c9-bf66-4f69-ad0b-b0f04e182de1

*** Original change description ***

Enable cquery in GitHub CI

BEGIN_PUBLIC

Enable cquery in GitHub CI

This will prevent incompatible targets from being built and tested.

END_PUBLIC

***

PiperOrigin-RevId: 727883315
Change-Id: Ia557c37847450e6748002da74f1de1cef4ffefb9
1 file changed
tree: 1bc22c2ed4697f31bfc917beecb862f4b1ac7de2
  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

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: