Fabian Meumertzheim
Fabian Meumertzheim
Your branch is not up-to-date: https://github.com/dynacondev/bazel-central-registry/tree/xplane_sdk/modules/rules_apple Rebasing onto `main` should solve this.
The regular C++ toolchain takes precedence without an explicit `bazel_dep` in the top-level module. @keith @brentleyjones How do you usually work around this?
Since v3.7.3 is already in the registry, is this PR still relevant? Happy to merge once the module maintainers tell me to.
Keyword-only arguments are also supported in Bazel's implementation of Starlark and, from what I can tell, frequently used, especially in the Starlarkification efforts. Citing @laurentlb from https://bazelbuild.slack.com/archives/CDCEKVCHY/p1678902971702729?thread_ts=1678902446.157669&cid=CDCEKVCHY > This can...
@mattyclarkson Wouldn't the module still be needed for the CGO version of circl? Have you observed a difference in performance?
Sure, but does gazelle generate the correct build files for it to find the assembly without a patch? That's what I introduced the module for in the first place.
@aaronmondal Windows is failing.
I'm working on a feature system for Bazel modules (similar to that from Cargo), which could be a way to make this configurable.
Cc @oquenchil