Move coverage script / flag to public package (#867)
Test rules that can produce coverage for transitive cc rules need to
reference this script with something like:
```bzl
"_collect_cc_coverage": attr.label(
default = "@rules_cc//cc/coverage:collect_cc_coverage",
executable = True,
cfg = config.exec(exec_group = "test"),
)
```
So it shouldn't be private.
Closes #867
COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/867 from keith:ks/move-coverage-script-flag-to-public-package 3c01cb716b13b59e569246749d031c46d0ab584b
PiperOrigin-RevId: 981202792
Change-Id: I977b04e69987c9bf022cfdf7594ea4e37d4788da
This repository contains C, C++, and Objective-C language support for the Bazel build system.
For this module's main reference, see the Bazel documentation.
Follow the official instructions to Install Bazel.
Add the latest release to your MODULE.bazel project file.
In a BUILD.bazel file, import and use the rules:
load("@rules_cc//cc:cc_binary.bzl", "cc_binary") cc_binary( name = "hello_world", srcs = ["hello_world.cc"], )
Build and run your C/C++ binary with one command:
$ bazel run hello_world
To build the project without running the binary, use Bazel's build subcommand:
$ bazel build hello_world
rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.
You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:
--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1
Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:
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