bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-25 17:31:30 +00:00
Code Issues Releases Activity
C++ Rules for Bazel
192 commits 15 branches 20 tags 1.9 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Find a file
Googler d562dc8046 CcSharedLibraryInfo propagates labels for exports now 
It used to propagate TransitiveInfoCollections for exports which is not ideal.

RELNOTES:none
PiperOrigin-RevId: 281056556
Change-Id: I2ec39292aefb55369720fbbb93ee1e2f8704b8db
2019-11-18 06:33:34 -08:00
.bazelci Adds integration test for cc_shared_library. 2019-11-15 05:36:47 -08:00
cc Fix codebase in preparation for incompatible_use_cc_configure_from_rules_cc 2019-11-12 04:35:10 -08:00
distro Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
examples CcSharedLibraryInfo propagates labels for exports now 2019-11-18 06:33:34 -08:00
third_party Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
tools Explicitly export files needed by other packages 2019-11-13 04:27:16 -08:00
.gitignore
BUILD
CODEOWNERS
CONTRIBUTING.md
internal_deps.bzl Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
internal_setup.bzl Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
ISSUE_TEMPLATE.md
LICENSE
README.md Add badge for incompatible flag pipeline 2019-11-04 12:38:06 +01:00
renovate.json Update renovate.json 2019-11-03 11:40:55 +01:00
WORKSPACE Fix call in WORKSPACE 2019-11-01 16:39:47 +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(
    ...
)

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: