commit | 31c46f250a9c8d845a1b4199a900512acf0ae3a7 | [log] [tgz] |
---|---|---|
author | Googler <aehlig@google.com> | Wed Nov 13 04:26:47 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 13 04:27:16 2019 -0800 |
tree | 850debc1609fea8c07a09a431598f8501aaa11f3 | |
parent | 8e88d89faf357212ab70e4df7de9bdff9411725b [diff] |
Explicitly export files needed by other packages Add an explicit export statement (with the same visibility) for files that are currently only implicitly exported and used by other pacakges. This prepares changing the visibility of implicitly-exported files to be package private without causing a breakage. PiperOrigin-RevId: 280171386 Change-Id: I083a9d4f82067b4d4c94d7b554013aeb91e401cc
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.
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( ... )
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
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
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:
#cc
on slack.bazel.build