bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
430 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
Googler 760de9ef32 Cleanup uses of ctoolchain migration 
BEGIN_PUBLIC
Internal change
END_PUBLIC

PiperOrigin-RevId: 606195771
Change-Id: I2c6ef2bd57991c6fe65e1bf49a67f3250c12724d
 		2024-02-12 03:16:53 -08:00
.bazelci Enable `//tests/...` in CI 2023-07-08 00:29:45 +02:00
.bcr
…
cc Create toolchain types for proto_library and lang_proto_library 2023-09-18 12:30:14 -07:00
examples Automatic code cleanup. 2023-09-18 03:04:35 -07:00
tests Fix internal breakages for `rules_cc`. 2024-02-09 09:50:57 -08:00
third_party Add support for expand_if_available for env_entry 2023-07-17 08:12:34 -07:00
tools/migration Cleanup uses of ctoolchain migration 2024-02-12 03:16:53 -08:00
.gitignore
…
AUTHORS
…
BUILD
…
CODEOWNERS
…
CONTRIBUTING.md
…
ISSUE_TEMPLATE.md
…
LICENSE
…
MODULE.bazel Update MODULE.bazel 2023-09-19 10:05:03 +02:00
README.md Update README.md 2023-07-19 15:32:02 -07:00
WORKSPACE Update dependency io_bazel_rules_go to v0.42.0 2023-09-30 01:55:50 +00:00
renovate.json
…

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: