Google Git
Sign in
bazel / rules_cc / 8f861e884c0003554b39fd0358293bbde3923ecd
commit8f861e884c0003554b39fd0358293bbde3923ecd[log] [tgz]
authorCopybara-Service <copybara-worker@google.com>Thu Oct 07 09:39:32 2021 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Oct 07 09:39:32 2021 -0700
treebb683a258b26402f89e5eb5cc65997bc6a794bc9
parentaa7ff810cf5ec99ca34f784743b33631b74c2d16 [diff]
parent890aeb2860814104ae0bc66373fa11f754280434 [diff]
Merge pull request #117 from meteorcloudy:bzlmod

PiperOrigin-RevId: 401534549
Change-Id: I977d26e05d3a04fbb2ee22ba021b3f1c00fa84b5
tree: bb683a258b26402f89e5eb5cc65997bc6a794bc9
  1. .bazelci/
  2. bzlmod/
  3. cc/
  4. examples/
  5. tests/
  6. third_party/
  7. tools/
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CODEOWNERS
  12. CONTRIBUTING.md
  13. internal_deps.bzl
  14. internal_setup.bzl
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags Build status

This repository contains 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/TODO"],
    sha256 = "TODO",
)

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

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: