commit | da4c91577af5bc9099403c48d68f91eb8b79ee88 | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Tue Jan 08 16:32:05 2019 +0100 |
committer | Marcel Hlopko <hlopko@google.com> | Wed Jan 09 08:59:42 2019 +0100 |
tree | 4a522fd42fe034b1b86a85b41d836f30d8dc8ccd | |
parent | 281a8bc480f99c86744c5b72172282fa6f86d7ed [diff] |
Add repository for py.mock to rules_cc RELNOTES: None. PiperOrigin-RevId: 228326658
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:rules.bzl", "cc_library") cc_library( ... )
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.