pc-windows-gnu

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.

That's why there's unique triplets for windows for whether or not you're compiling for msvc or gnu, as in x86_64-pc-windows-gnu vs.

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.

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.

I personally work on embedded ARM stuff on Windows, so I'm cross compiling from x86_64-pc-windows-gnu to thumbv7em-none-eabihf all the time.

Any bugs that show up in i686-pc-windows-gnu but neither of the other two are almost certainly MinGW-specific jank, rather than anything that could have security implications on other platforms.

I compile in Rust with --target x86_64-pc-windows-gnu and test under Wine.

Lately I've cross-compiled a few times Linux/Windows programs, and the only thing I had to do (assuming that the underlying crates are compatible, and that the development libraries are in place, which is required for any language) was: rustup target add x86_64-pc-windows-gnu rustup toolchain install stable-x86_64-pc-windows-gnu That's all.

The bindings to set it up gave hard to debug errors and there is no support for compiling the x86_64-pc-windows-gnu toolchain on anything else besides a windows system; Which makes sense but winapi-rs compiled on Linux so I stuck with it.

This for some reason includes stuff like "winapi-i686-pc-windows-gnu" which really has no place for a set of linux software tools.

Just get the repository with "git clone", and make sure you have Rust installed for target "x86_64-pc-windows-gnu".

I liked it because I was able to cross-compile to Windows from my Mac and from my Linux based CI with extreme ease ("cargo build --release --target x86_64-pc-windows-gnu").

If you try the piston getting started example on Windows (the spinning square), change the freetype name to "libfreetype.a" and put it in the 1.0 path: C:\Program Files\Rust stable 1.0\bin\rustlib\x86_64-pc-windows-gnu\lib Other than that it works.