Update to newer VC version - at least VS 2015

[rkeithhill]

With this change, the bat choco install would find vcredist 2015-2019 already installed on most Windows 10 systems.

[sharkdp]

Maybe this could be resolved by switching from windows-2019 to windows-2022?

bat/.github/workflows/CICD.yml

Lines 136 to 146 in 282b702

	- { target: aarch64-unknown-linux-gnu , os: ubuntu-20.04, use-cross: true }
	- { target: arm-unknown-linux-gnueabihf , os: ubuntu-20.04, use-cross: true }
	- { target: arm-unknown-linux-musleabihf, os: ubuntu-20.04, use-cross: true }
	- { target: i686-pc-windows-msvc , os: windows-2019 }
	- { target: i686-unknown-linux-gnu , os: ubuntu-20.04, use-cross: true }
	- { target: i686-unknown-linux-musl , os: ubuntu-20.04, use-cross: true }
	- { target: x86_64-apple-darwin , os: macos-10.15 }
	- { target: x86_64-pc-windows-gnu , os: windows-2019 }
	- { target: x86_64-pc-windows-msvc , os: windows-2019 }
	- { target: x86_64-unknown-linux-gnu , os: ubuntu-20.04 }
	- { target: x86_64-unknown-linux-musl , os: ubuntu-20.04, use-cross: true }

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources

[rkeithhill]

I'm sorry. I didn't realize this was a Rust-based utility. I see on the Rust repo this issue has come up - see:

rust-lang/rust#26258
rust-lang/rfcs#1061
volks73/cargo-wix#115

From this documentation PR it seems you could statically link the CRT on Windows and then there would be no need of the vcredist. I tried this on a simple Rust "hello world" program and it appears to work:

The exe size in bytes increased from 148480 (dynamically linked) to 250368 (statically linked) for a debug build. This might be worth exploring.

Also see these docs on Rust and statically linking CRT.

[sharkdp]

Thanks. The other option is to use the GNU toolchain. We also deploy executables which are built using that (bat-v0.20.0-x86_64-pc-windows-gnu.zip). There have been past discussions on this topic on this issue tracker. Might be valuable to summarize those here. I don't remember why we don't switch off the MSVC builds completely.

[Hrxn]

Thanks. The other option is to use the GNU toolchain. [..] There have been past discussions on this topic on this issue tracker. Might be valuable to summarize those here. I don't remember why we don't switch off the MSVC builds completely.

Switching off MSVC builds? Does this imply that the GNU builds are somehow more robust, or more performant, or something like that?