Add scratch workflow and runner script for rules_cc - Add a `scratch` workflow to `copy.bara.sky` to allow testing pending CLs in an external-style local directory. - Add `copybara_runner.sh` to automate the process of running Copybara and exporting to a scratch folder. - Add BUILD targets for the runner script to match the example pattern. Example usage: ``` blaze run //third_party/bazel_rules/rules_cc/cc/google:runner -- --workf low scratch --cl <CL_NUMBER> -o ~/scratch2/scratch_rules_cc_copybara ``` PiperOrigin-RevId: 907700364 Change-Id: Iba7ff0ed687d6b38d80fd39473f223acc1c5482a
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