You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, rules_ispc only supports the traditional WORKSPACE approach. I want to add Bzlmod support to this ruleset. When looking at other rulesets, such as rules_ruby the final usage of those rules could look like this in MODULE.bazel file:
I wonder if this is the proper way to go in bzlmod?
I have created an extension.bzl file:
"""Module extensions used by bzlmod"""ispc_toolchain=tag_class(attrs= {
"name": attr.string(doc="Base name for generated repositories, allowing multiple to be registered."),
"version": attr.string(doc="Explicit version of ISPC."),
})
def_ispc_module_extension(module_ctx):
registrations= {}
# Does it make sense to call here register_toolchains?# native.register_toolchains(...)# How can I do this for different pre-compiled binaries of ISPC?ispc=module_extension(
implementation=_ispc_module_extension,
tag_classes= {
"toolchain": ispc_toolchain,
},
)
I have also created a toolchain.bzl file that looks like this:
Currently, rules_ispc only supports the traditional
WORKSPACE
approach. I want to add Bzlmod support to this ruleset. When looking at other rulesets, such as rules_ruby the final usage of those rules could look like this inMODULE.bazel
file:In a BUILD file, I want then to use something like this:
I wonder if this is the proper way to go in bzlmod?
I have created an
extension.bzl
file:I have also created a
toolchain.bzl
file that looks like this:I am unsure how to connect the dots to get this working. Also, I am not sure if this is the right approach. Any hints are welcome.
The text was updated successfully, but these errors were encountered: