2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-26 20:02:22 +00:00
C++ Rules for Bazel
Find a file
Googler 19a278e626 Prepare for 0.0.12 release
PiperOrigin-RevId: 683189389
Change-Id: I6092c6d9716502cb236c307b9761d88a09b41334
2024-10-07 08:14:05 -07:00
.bazelci Enable //tests/... in CI 2023-07-08 00:29:45 +02:00
.bcr Add bazel version 2024-10-04 13:28:28 +02:00
cc Merge pull request #250 from bazelbuild:Wyverald-patch-1 2024-10-07 01:59:36 -07:00
docs Make stardoc a dev dependency 2024-10-04 15:07:57 +02:00
examples Sync cc toolchain from Bazel's tools/cpp 2024-10-03 09:32:38 -07:00
tests Create a concept of a tool capability. 2024-10-02 19:56:22 -07:00
third_party Add support for expand_if_available for env_entry 2023-07-17 08:12:34 -07:00
tools/migration Sync cc toolchain from Bazel's tools/cpp 2024-10-03 09:32:38 -07:00
.gitignore Sync cc toolchain from Bazel's tools/cpp 2024-10-03 09:32:38 -07:00
AUTHORS Create AUTHORS 2021-03-25 11:49:43 -04:00
BUILD Introduce flag --@rules_cc//:link_extra_libs 2023-02-16 04:15:10 -08:00
CODEOWNERS Merge pull request #146 from bazelbuild:meteorcloudy-patch-1 2022-09-19 13:51:00 +00:00
CONTRIBUTING.md Add initial content of rules_cc repo 2019-01-09 08:58:14 +01:00
ISSUE_TEMPLATE.md Fix issue template 2019-02-27 01:37:03 -08:00
LICENSE Internal change 2019-01-09 08:56:00 +01:00
MODULE.bazel Prepare for 0.0.12 release 2024-10-07 08:14:05 -07:00
README.md Update README.md 2023-07-19 15:32:02 -07:00
renovate.json Update renovate.json 2019-11-03 11:40:55 +01:00
WORKSPACE Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/238 2024-09-11 05:56:57 -07:00

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: