Return depset_file subjects from link_action inputs() and outputs() This is reflective of what they actually are and string formatting works appropriately (since we sometimes compare files and not strings, simply setting "format = True" when we create the collection subject does not work). The depset subject does not support transform() but this is almost always unnecessary and we can achieve what we need in other ways. If it's ever truly needed, we can always operate on the underlying data (which is still just a list) - maybe the depset subject could have a "as_list" method that returns a corresponding collection subject if this was ever needed. PiperOrigin-RevId: 963462988 Change-Id: I33772dc8b7efc89b8316303f0ae90f026352e3b6
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