Skip to content

Commit

Permalink
build: add support for native Windows ARM64 MSVC
Browse files Browse the repository at this point in the history
Visual Studio 2022 17.4 introduces native ARM64 support, including host
tools for MSVC. As this won't be supported on VS2019, this commit only
adds the detection logic for native ARM64 tools to vs-set-2022.

Refs: nodejs/build#2540
Refs: https://devblogs.microsoft.com/visualstudio/arm64-visual-studio/
  • Loading branch information
dennisameling committed Jan 28, 2023
1 parent f69e84c commit f7ca15b
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions vcbuild.bat
Original file line number Diff line number Diff line change
Expand Up @@ -253,6 +253,14 @@ if %target_arch%==x86 if %msvs_host_arch%==x86 set vcvarsall_arg=x86
:vs-set-2022
if defined target_env if "%target_env%" NEQ "vs2022" goto vs-set-2019
echo Looking for Visual Studio 2022
@rem Visual Studio 2022 17.4 added support for native host tools on ARM64
@rem https://devblogs.microsoft.com/visualstudio/arm64-visual-studio/
if _%PROCESSOR_ARCHITECTURE%_==_ARM64_ set msvs_host_arch=arm64
if _%PROCESSOR_ARCHITEW6432%_==_ARM64_ set msvs_host_arch=arm64
set vcvarsall_arg=%msvs_host_arch%_%target_arch%
if %target_arch%==x64 if %msvs_host_arch%==amd64 set vcvarsall_arg=amd64
if %target_arch%==x86 if %msvs_host_arch%==x86 set vcvarsall_arg=x86
if %target_arch%==arm64 if %msvs_host_arch%==arm64 set vcvarsall_arg=arm64
@rem VCINSTALLDIR may be set if run from a VS Command Prompt and needs to be
@rem cleared first as vswhere_usability_wrapper.cmd doesn't when it fails to
@rem detect the version searched for
Expand Down

0 comments on commit f7ca15b

Please sign in to comment.