Linking with param file on Windows fails with spaces in paths

[SimplyDanny]

Trying to build https://github.com/apple/swift-argument-parser with Bazel fails on Windows at the linking step, because file paths in param files contain spaces that llvm-lib.exe doesn't parse as complete paths.

I tried setting windows_quoting_for_param_files at several places, but it doesn't seem to be passed on to the code handling the quoting. Other experiments also didn't work. Likely, this option is even not the right one to look at, even though it sounds related.

I'm not even sure now that rules_swift is the place where this needs to be fixed. If someone has other ideas, let me know.

[keith]

The final link commands are actually handled by rules_cc, so i think something else has gone wrong, but it might still be on us with how we configure the toolchain with clang? im not sure yet

[SimplyDanny]

I read your article about Bazel rule debugging and it sounds like there's no better way than sprinkling print(...)s everywhere, or is there a few years later @keith?

[keith]

yea probably. in this case i would personally start by making sure that a normal cc_binary builds with everything else being the same.