rules_cc/cc/repositories.bzl

"""Repository rules entry point module for rules_cc."""

load("//cc/private/toolchain:cc_configure.bzl", "cc_configure")

def rules_cc_dependencies():
    pass

# buildifier: disable=unnamed-macro
def rules_cc_toolchains(*args):
    cc_configure(*args)
Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html RELNOTES: None. PiperOrigin-RevId: 253736769 Change-Id: Ib13ecb077559f890aa3cc207b7ec1a53ac18d553 2019-06-18 07:21:29 +00:00			`"""Repository rules entry point module for rules_cc."""`

Automated rollback of commit 48881f1f453c963e49044210bb1d09b354c83f67. * Reason for rollback * Broke a test * Original change description * 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... *** PiperOrigin-RevId: 501228335 Change-Id: I858dc3ea44df7ae70b5603f6dc2e082b4540c42a 2023-01-11 10:47:44 +00:00			`load("//cc/private/toolchain:cc_configure.bzl", "cc_configure")`
Add skylib dependency [Copybara import of https://github.com/bazelbuild/rules_cc/pull/10] Skylib will be used to check minimum supported Bazel version. Merge 2e5b5eb2d04a7a87970f6441c5b782e0954bea14 into 3723b4c35f361ba5593d00c1f4183b387402fef5 PiperOrigin-RevId: 240725578 2019-03-28 07:52:04 +00:00
Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html RELNOTES: None. PiperOrigin-RevId: 253736769 Change-Id: Ib13ecb077559f890aa3cc207b7ec1a53ac18d553 2019-06-18 07:21:29 +00:00			`def rules_cc_dependencies():`
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			`pass`
Add skylib dependency [Copybara import of https://github.com/bazelbuild/rules_cc/pull/10] Skylib will be used to check minimum supported Bazel version. Merge 2e5b5eb2d04a7a87970f6441c5b782e0954bea14 into 3723b4c35f361ba5593d00c1f4183b387402fef5 PiperOrigin-RevId: 240725578 2019-03-28 07:52:04 +00:00
Instead disable the buildifier warning 2020-05-04 09:45:39 +00:00			`# buildifier: disable=unnamed-macro`
Automated rollback of commit 48881f1f453c963e49044210bb1d09b354c83f67. * Reason for rollback * Broke a test * Original change description * 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... *** PiperOrigin-RevId: 501228335 Change-Id: I858dc3ea44df7ae70b5603f6dc2e082b4540c42a 2023-01-11 10:47:44 +00:00			`def rules_cc_toolchains(*args):`
			`cc_configure(*args)`