Andy Polyakov

It's not obvious that this is the right forum to discuss this problem. Because it appears to be a pure Rust problem. At least cc-rs is primarily about compiling C/C++...

Just in case, #728 is likely to be related. Maybe even making the current arrangement work?

> If anything, it would be more appropriate to have cc-rs interrogate Rust when choosing the compiler, not vice versa, as discussed in #693. Just in case, for completeness and...

You surely refer to the fact that Bourne shell won't let you set an environment variable with dot in its name. Which formally isn't an indication that `cc-rs` would fail...

All I'm saying is that formally you couldn't put it as "Specifically, this part failed:" in the original post :-) But of course one can legitimately make a case for...

The problem description is misleading. Would `cargo build --target=x86_64-pc-windows-msvc` work on Linux with pure Rust code? Without involving cc-rs that is. No(*). Is it going to be fixed? ... Does...

> It's definitely possible to cross compile Rust to msvc targets using `clang-cl`. Well, while Linux clang-cl is indeed capable of generating PE-COFF .obj files, you lack headers, libraries and...

> `llvm-link` can be used instead of `link.exe`. llvm-link is a bitcode linker. It won't emit PE-COFF (or any other) executable.

Oh! And so you mean that you'd be able to actually replace MSVC linker with it? Why doesn't clang-cl call it? BTW, Rust comes with lld-link. As far as I...

Wow! Well, it's still only one out of three missing components on Linux, headers, libraries, ~link.exe~. Yet I'd still argue that it makes less sense to make it, the cross-compilation...