commit | 34ca16f4aa4bf2a5d3e4747229202d6cb630ebab | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Thu Mar 12 11:07:56 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 12 11:08:12 2020 -0700 |
tree | ce261c88f119d0a479a11bea85473903ce8cb687 | |
parent | 7fdc27c099bd6e30bf8e112923c8f1b86acd34af [diff] |
Partially fix MacOS llvm coverage collection This allows setting GCOV on the command line to overwrite the default setting, which points to /usr/bin/gcov. In order to use this, you also need to disable the gcov coverage feature and enable the llvm coverage feature instead. The full command-line looks like this: GCOV=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/llvm-profdata bazel coverage --features=llvm_coverage_map_format --features=-gcc_coverage_map_format //cpp:test Progress on #10457. Original change by ulfjack RELNOTES: None. PiperOrigin-RevId: 300583709 Change-Id: Ibeda8469db6750fc9fc3bba60e19118a2e482ed8
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:
rules_cc
mailing list#cc
on slack.bazel.build