Andy Polyakov

> ring ... straight gas syntax .S files. But all the straight .S files you have don't target Windows, let alone Windows on ARM. Wouldn't it be more reasonable to...

Alternatively one can put is as following. If user tries to compile `.S` file in msvc environment, look up `clang` and use it. **Irregardless** which compiler is chosen. If lookup...

> So I can set our `AR` to `lld-link` No, set your `AR` to `llvm-lib`. General recommendation is to use `clang-cl` [for Windows compilations], in which case it will use...

> However, in our case we are using `lld-link /lib` which then acts as `llvm-lib`, just to make things interesting. Does it mean that you use it elsewhere? And/or that...

In case `llvm-lib` is not an option. Rustc relies on MSVC `link.exe`, but then there is MSVC `lib.exe` next to it, so **not** setting AR should work. Or setting it...

> In case `llvm-lib` is not an option. Rustc relies on MSVC `link.exe`, but then there is MSVC `lib.exe` next to it, so **not** setting AR should work. Or setting...

> Right, my first problem was finding link.exe and it's working now. I don't quite follow. Who links your final executable? If rustc, then it's supposed to find it all...

We have to recognize that the decision to use link.exe is rustc's own, cc-rs has no say in it. [Even the possibility to use lld-link is outside cc-rs's control.] cc-rs...

> `$AR` is consumed but not `$ARFLAGS` Are you looking for a street fight or something? :-) :-) :-) But on a serious note. ARFLAGS is a `make` thing, while...

> put this on ice for now One can probably make a case for defaulting for `llvm-ar` in case user chooses to use `clang`. As opposed to `clang-cl` that is....