Fix buildifier issues Copybara Import from https://github.com/bazelbuild/rules_cc/pull/794 BEGIN_PUBLIC Fix buildifier issues (#794) Closes #794 END_PUBLIC Tested: TAP --sample ran all affected tests and none failed [] COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/794 from keith:ks/fix-buildifier-issues 43d5399e2bc6065dcc97ce213dbdb11ebbedf917 PiperOrigin-RevId: 951198468 Change-Id: I43a6823b5e0160c77903d6ce25fb7a424b7ab81e
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