bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
rules_cc/MODULE.bazel

18 lines
592 B
Plaintext
Raw Normal View History

Modularize rules_cc
2021-10-06 16:09:19 +00:00
module(
name = "rules_cc",
Bump rules_cc version to 0.0.13 PiperOrigin-RevId: 684052002 Change-Id: I91de575a1ad021297787d00f9f95f0d569d9a5d8
2024-10-09 15:45:39 +00:00
version = "0.0.13",
The auto-configured toolchains provided by Bazel itself have diverged heavily from the version maintained in this repo. There is no need to maintain this duplication until Starlarkification has progressed succiciently for rules_cc to be the source of truth for them. This is particularly relevant for Bzlmod, which currently uses the toolchains defined in rules_cc. As a result, Bazel C++ builds will use subtly different toolchains depending on whether --enable_bzlmod is used or not. This is fixed by loading toolchain detection logic from @bazel_tools in the module extension. Closes #163 PiperOrigin-RevId: 501199523 Change-Id: I01f263d37495d0c5dd070c8a32945898d1d639c5
2023-01-11 08:11:34 +00:00
compatibility_level = 1,
Modularize rules_cc
2021-10-06 16:09:19 +00:00
)
Make toolchains use directory markers instead of strings. BEGIN_PUBLIC Make toolchains use directory markers instead of strings. You now refer to this instead of a string containing the repo mapped path. END_PUBLIC PiperOrigin-RevId: 639946886 Change-Id: I409be7b7002252b06562a2982a2568e79811877d
2024-06-03 23:19:58 +00:00
bazel_dep(name = "bazel_skylib", version = "1.7.1")
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/238 BEGIN_PUBLIC Copybara import of the project: -- 2803a12428e6493e48176f46f352a3e78820e7da by Ivo List <ilist@google.com>: Prepare for release 0.0.10-rc2 -- 3423c7320893a84a5166aa9962ce57c3715c4660 by Ivo List <ilist@google.com>: Format WORKSPACE -- a99403a6b0ee72aea634b84b3caa065a9290a6fb by Ivo List <ilist@google.com>: Touch module -- 258d8c9f2410796715cb8fe8a07e2dacf9b217e0 by Ivo List <ilist@google.com>: Revert "Touch module" This reverts commit a99403a6b0ee72aea634b84b3caa065a9290a6fb. END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/238 from comius:release-0.0.10-rc2 258d8c9f2410796715cb8fe8a07e2dacf9b217e0 PiperOrigin-RevId: 673358956 Change-Id: Iabc9c29e6f168cfdfd2f0657438b71654f470cc9
2024-09-11 12:56:07 +00:00
bazel_dep(name = "platforms", version = "0.0.10")
Redirect cc_proto_library to protobuf PiperOrigin-RevId: 683876696 Change-Id: I0444b3b3bc3ac67bb641d82fe1d67117a6e2bcae
2024-10-09 04:17:42 +00:00
bazel_dep(name = "protobuf", version = "27.0")
Modularize rules_cc
2021-10-06 16:09:19 +00:00
Sync cc toolchain from Bazel's tools/cpp - @bazel_tools//tools/cpp:toolchain_type is not moved. - Added cc/toolchains/toolchain_config_utils.bzl for exposing util functions for cc toolchain configuration. Closes https://github.com/bazelbuild/rules_cc/pull/247 Working towards https://github.com/bazelbuild/bazel/issues/23809 PiperOrigin-RevId: 681913803 Change-Id: I16ff456a212ab0e579c137bd74344255f4e49bd8
2024-10-03 16:31:57 +00:00
cc_configure = use_extension("//cc:extensions.bzl", "cc_configure_extension")
use_repo(cc_configure, "local_config_cc", "local_config_cc_toolchains")
Update MODULE.bazel
2023-09-19 08:05:03 +00:00
Fix MODULE.bazel file The next release for rules_cc would be 0.0.3, and migrate to new toolchain registration API.
2022-09-19 12:00:24 +00:00
register_toolchains("@local_config_cc_toolchains//:all")
Copybara Merge: https://github.com/bazelbuild/rules_cc/pull/165 BEGIN_PUBLIC Copybara import of the project: -- 56e69b82484f1a9fb55d8173cc112f9f608f3581 by Fabian Meumertzheim <fabian@meumertzhe.im>: Simplify WORKSPACE setup and update ancient deps By removing a single unused `bzl_library` target, rules_cc no longer has any dependencies that would need to be loaded by a dependency macro. The existing macro is made a no-op. The few needed Bazel Federation dependencies are inlined and, in the case of bazel_skylib and abseil-py, updated to modern versions. Also reorders `WORKSPACE` to list direct dependencies first and keeps `MODULE.bazel` in sync with the dependency versions used in WORKSPACE. The `ubuntu1604` CI pipeline is removed as the version of Python used by it is no longer supported and the distribution is EOL. Instead, a new pipeline is added to check the Bzlmod build. END_PUBLIC COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/165 from fmeum:fix-workspace-module 56e69b82484f1a9fb55d8173cc112f9f608f3581 PiperOrigin-RevId: 501245864 Change-Id: Ib71ad910705807a00929a76774387a38d2da0f9f
2023-01-11 12:32:58 +00:00
BEGIN_PUBLIC Add support for testing rules_cc's new toolchains with rules_testing. END_PUBLIC PiperOrigin-RevId: 608769646 Change-Id: I1a698355e5e977cc86eedc7cf6e8e0f888593cb8
2024-02-20 23:53:42 +00:00
bazel_dep(name = "rules_testing", version = "0.6.0", dev_dependency = True)
Make stardoc a dev dependency Otherwise rules_cc is transitively incompatible with Bazel 6 through the chain stardoc 0.7.0 -> rules_java 7.6.1. `stardoc` targets are not needed by consumers of the ruleset.
2024-10-01 06:32:55 +00:00
bazel_dep(name = "stardoc", version = "0.7.0", dev_dependency = True)