Win arm64

[isuruf]

We are getting rid of some hacks we had for other platforms

• ucrt is not used as win-arm64 is supported only for windows>=10 and ucrt DLLs are in the system and the ones in the
  system always takes precedence
• vs2015_runtime is renamed to vc14_runtime and vs2015_runtime is kept for compatibility in x86
• added a new vs_win-64=2022 output

[conda-forge-webservices]

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.

I do have some suggestions for making it better though...

For recipe:

• It looks like the 'vs2015_version' output doesn't have any tests.
• It looks like the 'vc' output doesn't have any tests.

[isuruf]

cc @conda-forge/core, @conda-forge/staged-recipes, @chenghlee

[xhochy]

Looking good!

[chenghlee]

vs*_runtime -> vc*_runtime naming change make sense to me; the new name is far more descriptive of what's actually in the package. I'll open a ticket to make sure similar changes are made to Anaconda's main channel.

[isuruf]

Thanks.

[h-vetinari]

Getting a bunch of clobber warnings, I suspect related to this PR:

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/win-64::vc14_runtime-14.34.31931-h5081d32_13, conda-forge/win-64::vs2015_runtime-14.34.31931-h4c5c07a_11
  path: 'library/bin/concrt140.dll'

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/win-64::vc14_runtime-14.34.31931-h5081d32_13, conda-forge/win-64::vs2015_runtime-14.34.31931-h4c5c07a_11
  path: 'library/bin/msvcp140.dll'

[and so on]

[h-vetinari]

Interestingly, it also appears to clobber the package artefacts itself, which would seem to imply that the required libs aren't there anymore when the "environment snapshot" after building is taken, and so conda thinks those libs belong to whatever artefact is being packaged:

ClobberWarning: Conda was asked to clobber an existing path.
  source path: C:\Miniforge\pkgs\vs2015_runtime-14.34.31931-h4c5c07a_11\Library\bin\concrt140.dll
  target path: D:\bld\boost-split_1683161338849\_test_env\Library\bin\concrt140.dll

[h-vetinari]

I also see this showing up in the CI on PRs that were merged to main, e.g. here, meaning that this will percolate to our published windows builds very quickly.

[h-vetinari]

Good news: I think we're not actually repackaging the windows-libs in regular artefacts, which takes off a lot of the pressure.

It seems I misread the way the clobberwarnings are emitted (in two parts).

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/win-64::vc14_runtime-14.34.31931-h5081d32_13, conda-forge/win-64::vs2015_runtime-14.34.31931-h4c5c07a_11
  path: 'library/bin/concrt140.dll'

[...]

ClobberWarning: Conda was asked to clobber an existing path.
  source path: C:\Miniforge\pkgs\vs2015_runtime-14.34.31931-h4c5c07a_11\Library\bin\concrt140.dll
  target path: D:\bld\boost-split_1683161338849\_test_env\Library\bin\concrt140.dll  # this one will be adapted to whatever feedstock we're in

[h-vetinari]

Ah, Isuru has a fix, thanks for the super quick response!