Skip to content

UebelAndre/rules_cc

This branch is 61 commits behind bazelbuild/rules_cc:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

8395ec0 · Nov 19, 2024
Nov 11, 2024
Oct 4, 2024
Nov 7, 2024
Nov 19, 2024
Nov 7, 2024
Nov 6, 2024
Nov 19, 2024
Sep 6, 2024
Nov 19, 2024
Nov 19, 2024
Mar 25, 2021
Nov 6, 2024
Oct 24, 2024
Jan 9, 2019
Feb 27, 2019
Jan 9, 2019
Nov 19, 2024
Aug 14, 2024
Nov 19, 2024
Oct 30, 2024
Nov 3, 2019

Repository files navigation

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:

About

C++ Rules for Bazel

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Starlark 83.0%
  • C++ 7.5%
  • Shell 5.4%
  • Smarty 4.0%
  • Batchfile 0.1%