Bump apple_support dep (#903) We switched the default toolchain to a rules based one moving forward. This also required a integration test change since previously the rules based toolchain files weren't in the integration test inputs, but now they are required. Closes #903 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/903 from keith:ks/bump-apple_support-dep 554150404db1a2bf78b64eac348fa9ee64559feb PiperOrigin-RevId: 991449012 Change-Id: I54fbdb4a8e726e03186340f4ec27e33a9ac8aad3
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