bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
343 Commits 15 Branches 20 Tags 1.9 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Go to file
Yun Peng 74f87ea2ba
Fix MODULE.bazel file 
The next release for rules_cc would be 0.0.3, and migrate to new toolchain registration API.
 		2022-09-19 14:00:24 +02:00
.bazelci Remove unnecessary tests from rules_cc 2022-03-17 04:50:16 -07:00
cc Update WORKSPACE: 2022-08-26 15:46:53 -04:00
examples Automatic code cleanup. 2022-06-22 06:02:29 -07:00
tests Internal change 2020-11-02 13:19:59 -08:00
third_party Add optional tool_path_origin to Tools in C++ crosstool 2020-05-06 06:52:27 -07:00
tools Update `cfg` values to make buildifier happy. 2022-05-18 09:16:43 -07:00
.gitignore Add things needed for rules_cc to build & test in the open 2019-01-09 08:59:09 +01:00
AUTHORS Create AUTHORS 2021-03-25 11:49:43 -04:00
BUILD Internal change 2020-11-02 13:19:59 -08:00
CODEOWNERS Update CODEOWNERS 2020-09-22 14:26:08 +02: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 Fix MODULE.bazel file 2022-09-19 14:00:24 +02:00
README.md Update rules_cc doc references for inclusive-language-fixit-2 2021-10-26 14:16:20 -07:00
WORKSPACE linty 2022-09-01 12:27:58 -04:00
internal_deps.bzl Remove dependency on rules_pkg from rules_cc 2021-10-05 09:13:17 -07:00
internal_setup.bzl Remove dependency on rules_pkg from rules_cc 2021-10-05 09:13:17 -07:00
renovate.json Update renovate.json 2019-11-03 11:40:55 +01:00

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: