pc-windows-msvc

There used to be four Tier 1 Windows targets, and there are still three: i686-pc-windows-msvc, x86_64-pc-windows-gnu, and x86_64-pc-windows-msvc.

Without std there is nothing to do, i586-pc-windows-msvc/gnu already work just fine - the PE format hasn't changed, really.

Target triples are of the form arch-vendor-kernel, and the -kernel is sometimes in the form -kernel-abi) So you can have x86_64-pc-windows-gnu or x86_64-pc-windows-msvc or x86_64-apple-darwin with the vendor field set.

We use the system linker, and so cross compiling to x86_64-pc-windows-msvc is tough, because link.exe won’t run outside of Windows, for example.

I switched scryer-prolog from `x86_64-pc-windows-gnu` to `x86_64-pc-windows-msvc` and got a binary size reduction of 10x, from 100MB to 10MB.

Aren't there also linker issues with cross-building for some targets like i686-pc-windows-msvc?

Window Defender don't allow the download of this file: ruxguitar-x86_64-pc-windows-msvc.zip.

Can one link two rust static libraries communicating with actual rust symbols (not just C ones), one built with gcc-rs (assuming that this is possible yet), the other built with rustc with its default x86_64-pc-windows-msvc abi?

> The tl;dr; of this change is that there is a new target of the compiler, > x86_64-pc-windows-msvc, which will not interact with the MinGW toolchain at > all and will instead use link.exe to assemble output artifacts.

Doing a 'cargo build' on Windows 10 x64 running Rust 1.79 x86_64-pc-windows-msvc gives me an error "error[E0433]: failed to resolve: could not find `unix` in `os`" referencing "server\src\infra\configuration.rs:239:22".

I'm seeing the same problem on Windows: $ rustup component add rustfmt error: toolchain 'stable-x86_64-pc-windows-msvc' does not contain component 'rustfmt' for target 'x86_64-pc-windows-msvc' I looked for how to uninstall rust, and found that "the book" says that the command 'rustup self uninstall' will uninstall both rust and rustup.

Because an arbitrary "too old" moniker is not something I've seen happening, and the only target that was removed instead of demoted in recent times was i586-pc-windows-msvc, aka Windows 10 without SSE, which was...utterly pointless since Windows 10 requires SSE.

If you want to try out the new features coming in v0.1.9 (including this one), you can follow the build steps from the readme on the master branch or download a zip containing the compiled binaries of the latest development build[2] by clicking on the green "tick" icon next to the latest commit and downloading the "komorebi-x86_64-pc-windows-msvc" artifact.