Google Git
Sign in
bazel / rules_cc / 475a3539c4cf6370b600a1ca423008bac0a01147
commit475a3539c4cf6370b600a1ca423008bac0a01147[log] [tgz]
authorYun Peng <pcloudy@google.com>Mon Nov 18 02:53:31 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Nov 18 02:54:44 2024 -0800
treee8d59cd4db153fa7ea9c748fc38c8a2d8b9f5f4a
parenta0e347f493f144b936c259718ef3e5cf8c451f0c [diff]
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/275

BEGIN_PUBLIC
Copybara import of the project:

--
e4857939bdbcbd9acb2bda5db8716b089f160847 by Yun Peng <pcloudy@google.com>:

Use full path for dirname and basename in osx_cc_wrapper.sh.tpl

Context: https://github.com/bazelbuild/rules_rust/pull/2998

END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/275 from bazelbuild:meteorcloudy-patch-4 e4857939bdbcbd9acb2bda5db8716b089f160847
PiperOrigin-RevId: 697557587
Change-Id: I6ceb3d5f0fd747acb758926750fa48493edbdf3e
1 file changed
tree: e8d59cd4db153fa7ea9c748fc38c8a2d8b9f5f4a
  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: