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

14 lines
440 B
Plaintext
Raw Normal View History

Modularize rules_cc
2021-10-06 16:09:19 +00:00
module(
name = "rules_cc",
Bump version
2022-09-23 14:42:18 +00:00
version = "0.0.4",
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
)
Update dependency platforms to v0.0.7
2023-07-28 21:37:53 +00:00
bazel_dep(name = "platforms", version = "0.0.7")
Modularize rules_cc
2021-10-06 16:09:19 +00:00
Register cc toolchain from @bazel_tools The one located in rules_cc isn't yet in sync.
2023-09-19 07:57:24 +00:00
cc_configure = use_extension("@bazel_tools//tools/cpp:cc_configure.bzl", "cc_configure_extension")
use_repo(cc_configure, "local_config_cc", "local_config_cc_toolchains")
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
Fix MODULE.bazel formatting Required due to a new buildifier release.
2023-01-09 12:52:42 +00:00
bazel_dep(name = "bazel_skylib", version = "1.3.0", dev_dependency = True)