Output file gets a `.pyd.dll` extension on Windows

[TendTo]

The pipeline that used to work on version 3.0.0 of pybind11_bazel stopped working on windows as soon as I upgraded to version 3.0.1.
Based on my observations, it seems that the issue is that, on windows, the output file, which should be <name>.pyd, becomes <name>.pyd.dll instead.

[Mizux]

which version of bazel and rules_cc did you use ?

[TendTo]

I used bazel 8.6.0 and rules_cc version 0.2.17.
If you could use more info, I can also share the MODULE.bazel.

This is the BUILD file I'm running into problems with, although I admit it's pretty involved: https://github.com/TendTo/lucid/blob/main/bindings/pylucid/BUILD.bazel.

[Mizux]

.pyd builtin support has been introduced in rule_cc 0.2.17 and bazel 9.0.0 cf #129

[TendTo]

I should be a bit more clear in how the problem manifested itself. The compilation is successful, and the file is generated correctly. But for some reason, it seems that, when I use the pybind rule in any context, it refers to a <name>.pyd.dll file, which is not the expected <name>.pyd.

E.g.

# Just a thin wrapper over
pybind_extension(
    name = "_constants",
    srcs = ["constants.cpp"],
)

genrule(
    name = "mygen",
    srcs = [
        ":_constants",
    ],
    cmd = "$(location :my_tool) --lib $(locations :_constants)",
    cmd_bat = "$(location :my_tool) --lib $(locations :_constants)", # $(locations :_constants) resolves to an existing but unexpected `_constants.pyd.dll`
    tools = [":my_tool"],
)