Honor object extensions for ThinLTO merged artifacts (#853) The ThinLTO merged object is hard-coded with an `.o` suffix even when the toolchain configures `.obj` for object files. This leaves clang-cl/MSVC action graphs with `.obj` compilation outputs but a `.o` indexing output and final-link input. Derive the merged artifact suffix from the toolchain's `OBJECT_FILE` artifact category. Unix toolchains keep the default `.o`. Focused analysis coverage configures `.obj` and checks both the indexing output and final-link input. Closes #853 COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/853 from cerisier:cerisier/thinlto-merged-object-extension 58053078f34d1f025c6d9a97b54ea060c006da37 PiperOrigin-RevId: 968965384 Change-Id: I7868b32b2f0368421029d578da04add3f016ebdc
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