Follow the guidelines below for building Electron on Windows.
vs2019_install = DRIVE:\path\to\Microsoft Visual Studio\2019\Community, replacing
Communitywith your installed versions and replacing
DRIVE:with the drive that Visual Studio is on. Often, this will be
WINDOWSSDKDIR = DRIVE:\path\to\Windows Kits\10, replacing
DRIVE:with the drive that Windows Kits is on. Often, this will be
symstore.exeis used for creating a symbol store from
Individual Components, scroll down and select the appropriate Windows SDK to install. Another option would be to look at the Windows SDK and emulator archive and download the standalone version of the SDK respectively.
Programs and Features→ Select the "Windows Software Development Kit" →
Change→ Check "Debugging Tools For Windows" →
Change. Or, you can download the standalone SDK installer and use it to install the Debugging Tools.
If you don't currently have a Windows installation, dev.microsoftedge.com has timebombed versions of Windows that you can use to build Electron.
Building Electron is done entirely with command-line scripts and cannot be done with Visual Studio. You can develop Electron with any editor but support for building with Visual Studio will come in the future.
Note: Even though Visual Studio is not used for building, it's still required because we need the build toolchains it provides.
Windows Security doesn't like one of the files in the Chromium source code (see https://crbug.com/441184), so it will constantly delete it, causing
gclient sync issues. You can exclude the source tree from being monitored by Windows Security by following these instructions.
To build for the 32bit target, you need to pass
target_cpu = "x86" as a GN arg. You can build the 32bit target alongside the 64bit target by using a different output directory for GN, e.g.
out/Release-x86, with different arguments.
$ gn gen out/Release-x86 --args="import(\"//electron/build/args/release.gn\") target_cpu=\"x86\""
The other building steps are exactly the same.
To generate a Visual Studio project, you can pass the
--ide=vs2017 parameter to
$ gn gen out/Testing --ide=vs2017
If you encountered an error like
Command xxxx not found, you may try to use the
VS2015 Command Prompt console to execute the build scripts.
Make sure you have the latest Visual Studio update installed.
Try reinstalling 32bit Node.js.
Creating that directory should fix the problem:
$ mkdir ~\AppData\Roaming\npm
You may get this error if you are using Git Bash for building, you should use PowerShell or VS2015 Command Prompt instead.
node.js has some extremely long pathnames, and by default git on windows doesn't handle long pathnames correctly (even though windows supports them). This should fix it:
$ git config --system core.longpaths true
This can happen during build, when Debugging Tools for Windows has been installed with Windows Driver Kit. Uninstall Windows Driver Kit and install Debugging Tools with steps described above.
Make sure you have installed
pip install pywin32.
This bug is a "feature" of Windows' command prompt. It happens when clicking inside the prompt window with
QuickEdit enabled and is intended to allow selecting and copying output text easily. Since each accidental click will pause the build process, you might want to disable this feature in the command prompt properties.
© GitHub Inc.
Licensed under the MIT license.