Bug: 290981549

Clone this repo:
  1. 7a77e62 OWNERS -> Kleaf team. am: 0c1d385edd by HONG Yifan · 5 months ago main master
  2. 0c1d385 OWNERS -> Kleaf team. by HONG Yifan · 5 months ago
  3. 27922a4 Upgrade bazelbuild-rules_cc to f88663dc502aacb6a6f377030d0652309412c8a9 am: 5d626dcf48 am: 886e2dee25 by Armando Montanez · 7 months ago android15-tests-dev aml_art_350913340 aml_art_351011240 aml_cbr_350910020 aml_doc_350915120 aml_ext_350912020 aml_hef_350921160 aml_med_350914000 aml_net_350911020 aml_per_350910080 aml_rkp_350910000 aml_sdk_350910000 aml_sta_350911020 aml_tet_350911120 aml_uwb_350911040 aml_wif_350912040
  4. 886e2de Upgrade bazelbuild-rules_cc to f88663dc502aacb6a6f377030d0652309412c8a9 am: 5d626dcf48 by Armando Montanez · 7 months ago
  5. 5d626dc Upgrade bazelbuild-rules_cc to f88663dc502aacb6a6f377030d0652309412c8a9 by Armando Montanez · 7 months ago main-kernel-build-2024

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: