bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-12-04 05:03:18 +00:00
Code Issues Releases Activity
C++ Rules for Bazel
585 commits 16 branches 20 tags 2 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Find a file
Googler 1698d2bf3a Apply external repo transforms to all migrated files 
This ensures that markdown files also have //third_party/* labels changed to external-friendly @foo// labels.

PiperOrigin-RevId: 694229457
Change-Id: I7f3bd56f0a196112a82159d6f47f8285049fc324
2024-11-07 13:29:51 -08:00
.bazelci Remove bad target 2024-11-06 14:19:32 +01:00
.bcr Add bazel version 2024-10-04 13:28:28 +02:00
.github/workflows Add release automation for rules_cc 2024-11-07 03:17:54 -08:00
cc Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/269 2024-11-07 05:14:59 -08:00
docs Apply external repo transforms to all migrated files 2024-11-07 13:29:51 -08:00
examples Remove defs.bzl usages 2024-11-06 07:35:53 -08:00
tests Fix rules_shell copybara 2024-11-06 07:36:04 -08:00
.bazelignore Rule-based toolchain example 2024-09-06 11:08:58 -07:00
.gitignore Update ignore all bazel-generated dirs 2024-10-03 10:10:35 -07:00
AUTHORS Create AUTHORS 2021-03-25 11:49:43 -04:00
BUILD Remove defs.bzl usages 2024-11-06 07:35:53 -08:00
CODEOWNERS Update CODEOWNERS for rules_cc 2024-10-24 07:37:56 -07: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 Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/269 2024-11-07 05:14:59 -08:00
README.md Update README.md 2024-08-14 14:57:09 -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/269 2024-11-07 05:14:59 -08:00
WORKSPACE.bzlmod Remove cc_proto_library from defs.bzl 2024-10-30 09:22:18 -07:00

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: