Keith Smiley
Keith Smiley
The intent of these checks was that if the C++20 version of this feature are enabled to execute the top codepath. libstdc++ 12 defines this feature as: ```cpp // in:...
Currently these are split into 3 rules because 1 rule cannot add 3 load statements and this repo doesn't have a defs.bzl that exposes them all
With bazel 8.x these should now be loaded externally. It's currently only a soft requirement, but at this point all users should start migrating to this.
In our project we don't use `experimental_index_url`, but through pulling in `rules_mypy` which does use it here https://github.com/theoremlp/rules_mypy/blob/c7c113c3608bc7569493c2abbff9aaa18119e145/MODULE.bazel#L29, our project's root pip.parse uses stopped working, because a platform specific variant...
Currently if you're writing custom rules that depend on python, it can be useful to extract things from the underlying python toolcahin like `toolchain.py3_runtime.interpreter`. I think it would be useful...
This was removed with bazel 8.x and exists in rules_android now
Depending on your project statically linking libstdc++ from your sysroot might not be viable. For example if you rely on other shared libraries that link the shared version, linking the...
With bazel 8.x cc_configure.bzl has moved to rules_cc
This has been removed from bazel 8.x, and is included in rules_android now
Currently `@rules_cc//cc/toolchains/actions:compile_actions` doesn't contain `@rules_cc//cc/toolchains/actions:objc_compile`. If I want to define a toolchain that supports `objc_compile`, I would expect to be able to create `cc_args` like this: ```bzl cc_args( name =...