|author||Googler <firstname.lastname@example.org>||Wed Oct 06 12:12:05 2021 -0700|
|committer||Copybara-Service <email@example.com>||Wed Oct 06 12:12:31 2021 -0700|
Make cc_shared_library use the builtin Starlark version Eventually, when we are ready to pull out all the other rules to an external repository cc_shared_library will be moved with the others: cc_library, cc_binary,... RELNOTES:none PiperOrigin-RevId: 401307125 Change-Id: I14f48a7753598eaa4269554e87351a70f75111c2
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
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( ... )
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()
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \ --input=my_toolchain/CROSSTOOL \ --inline
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: