move to vs2019/vc142

[h-vetinari]

Action item from the core meeting just now.

Full discussion is in conda-forge/conda-forge.github.io#1732. The important part is that this is ABI-compatible with all currently deployed windows artefacts (in fact, many feedstocks are using vs2019 already and happily mixing with vs2017 builds), so we do not need a migration.

Closes conda-forge/conda-forge.github.io#1732

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[h-vetinari]

@conda-forge/core
Per the announcement two weeks ago, we should merge this PR today (assuming no complaints arrived).

[isuruf]

Did you check that nvcc=10.2 works with vc142 toolchain?

[h-vetinari]

Did you check that nvcc=10.2 works with vc142 toolchain?

Has been running without issue for at least 1.5 years (example from faiss: conda-forge/faiss-split-feedstock@15fe1bf)

[h-vetinari]

Did you check that nvcc=10.2 works with vc142 toolchain?

Has been running without issue for at least 1.5 years (example from faiss: conda-forge/faiss-split-feedstock@15fe1bf)

aaaaaargh, sorry, spoke too soon. conda-forge only did cuda-on-win for nvcc=11.0+ 🤦

[leofang]

@h-vetinari vc2019 hates CUDA 11.2: conda-forge/cupy-feedstock#179 (comment)