Windows on ARM

    If your app doesn’t use any native modules, then it’s really easy to create an Arm version of your app.

    1. Make sure that your app’s node_modules directory is empty.
    2. Using a Command Prompt, run set npm_config_arch=arm64 before running npm install/yarn install as usual.
    3. If you have Electron installed as a development dependency, npm will download and unpack the arm64 version. You can then package and distribute your app as normal.

    General considerations

    Lots of Windows-specific code contains if… else logic that selects between either the x64 or x86 architectures.

    If you want to target arm64, logic like this will typically select the wrong architecture, so carefully check your application and build scripts for conditions like this. In custom build and packaging scripts, you should always check the value of npm_config_arch in the environment, rather than relying on the current process arch.

    Native modules

    If you use native modules, you must make sure that they compile against v142 of the MSVC compiler (provided in Visual Studio 2017). 您还必须检查 native module 提供或引用的 .dll 或 .lib 文件是否可用于 Arm 上的 Windows。

    Node.js/node-gyp

    Node.js v12.9.0 or later is recommended. If updating to a new version of Node is undesirable, you can instead to version 5.0.2 or later, which contains the required changes to compile native modules for Arm.

    Visual Studio 2017 (any edition) is required for cross-compiling native modules. You can download Visual Studio Community 2017 via Microsoft’s Visual Studio Dev Essentials program. After installation, you can add the Arm-specific components by running the following from a Command Prompt:

    Creating a cross-compilation command prompt

    Setting in the environment creates the correct arm64 .obj files, but the standard Developer Command Prompt for VS 2017 will use the x64 linker. To fix this:

    1. Duplicate the x64_x86 Cross Tools Command Prompt for VS 2017 shortcut (e.g. by locating it in the start menu, right clicking, selecting Open File Location, copying and pasting) to somewhere convenient.
    2. Change the Target field to read vcvarsamd64_arm64.bat at the end instead of vcvarsamd64_x86.bat.

    If done successfully, the command prompt should print something similar to this on startup:

    Linking against the correct node.lib

    By default, node-gyp unpacks Electron’s node headers and downloads the x86 and x64 versions of node.lib into , but it does not download the arm64 version (.) To fix this:

    1. Download the arm64 node.lib from https://electronjs.org/headers/v6.0.9/win-arm64/node.lib
    2. Move it to %APPDATA%\..\Local\node-gyp\Cache\6.0.9\arm64\node.lib

    Substitute 6.0.9 for the version you’re using.

    Cross-compiling native modules

    After completing all of the above, open your cross-compilation command prompt and run set npm_config_arch=arm64. Then use npm install to build your project as normal. As with cross-compiling x86 modules, you may need to remove node_modules to force recompilation of native modules if they were previously compiled for another architecture.

    Debugging native modules can be done with Visual Studio 2017 (running on your development machine) and corresponding Visual Studio Remote Debugger running on the target device. To debug:

    1. 在目标设备上通过命令提示符启动 .exe 应用(传递 参数可以在加载任何 native modules 之前暂停应用)。
    2. Launch Visual Studio 2017 on your development machine.
    3. 通过选择 调试 > 访问并输入设备的 IP 地址和 Visual Studio 远程调试器工具显示的端口号，连接到目标设备。
    4. Click Refresh and select the .
    5. You may need to make sure that any symbols for native modules in your app are loaded correctly. 要配置此内容，请进入 Visual Studio 2017Debug > Options…，and add the folders containing your .pdb symbols under Debugging > Symbols.

    Getting additional help