Ir para o conteúdo principal

Instruções para Configuração (Windows)

Follow the guidelines below for building Electron itself on Windows, for the purposes of creating custom Electron binaries. For bundling and distributing your app code with the prebuilt Electron binaries, see the application distribution guide.

Pré-requisitos​

  • Windows 10 / Server 2012 R2 ou superior
  • Visual Studio 2019 (>=16.0.0) to build, but Visual Studio 2022 (>=17.0.0) is preferred - download VS 2022 Community Edition for free
    • See the Chromium build documentation for more details on which Visual Studio components are required.
    • If your Visual Studio is installed in a directory other than the default, you'll need to set a few environment variables to point the toolchains to your installation path.
      • vs2022_install = DRIVE:\path\to\Microsoft Visual Studio\2022\Community, replacing 2022 and Community with your installed versions and replacing DRIVE: with the drive that Visual Studio is on. Often, this will be C:.
      • WINDOWSSDKDIR = DRIVE:\path\to\Windows Kits\10, replacing DRIVE: with the drive that Windows Kits is on. Often, this will be C:.
  • Node.js
  • Git
  • Debugging Tools for Windows of Windows SDK 10.0.15063.468 if you plan on creating a full distribution since symstore.exe is used for creating a symbol store from .pdb files.
    • Different versions of the SDK can be installed side by side. To install the SDK, open Visual Studio Installer, select Modify → 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.
    • As Ferramentas de Depuração do SDK também devem ser instaladas. If the Windows 10 SDK was installed via the Visual Studio installer, then they can be installed by going to: Control Panel → Programs → Programs and Features → Select the "Windows Software Development Kit" → Change → 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, developer.microsoft.com has timebombed versions of Windows that you can use to build Electron.

A configuração do Electron é feita totalmente por linha de comando, não é possível fazer pelo o Visual Studio. Você pode desenvolver com Electron utilizando qualquer editor, futuramente haverá suporte para o Visual Studio.

Note: Mesmo que o Visual Studio não seja utilizado para desenvolver com Electron, ainda é preciso ter instalado. required Porque é necessário a toolchains fornecida.

Exclude source tree from Windows Security​

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.

Compilando​

See Build Instructions: GN

Compilação 32bit​

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\""

Os outros passos para a compilação são os mesmos.

Projeto Visual Studio​

To generate a Visual Studio project, you can pass the --ide=vs2017 parameter to gn gen:

$ gn gen out/Testing --ide=vs2017

Solução de Problemas​

Comando xxxx não encontrado​

Se você encontrar um erro parecido com Command xxxx not found, você pode tentar usar o console do Prompt de Comando do VS2015 para executar os scripts do build.

Erro fatal do compilador interno: C1001​

Verifique se você tem a atualização mais recente do Visual Studio instalada.

LNK1181: não é possível abrir o arquivo 'kernel32.lib'​

Tente reinstalar o Node.js 32bit.

Erro: ENOENT, stat 'C:\Users\USERNAME\AppData\Roaming\npm'​

Creating that directory should fix the problem:

$ mkdir ~\AppData\Roaming\npm

node-gyp não é reconhecido como um comando interno ou externo​

Você pode obter este erro se você estiver usando Git Bash para construção, você deve usar o PowerShell ou VS2015 Command Prompt.

cannot create directory at '...': Filename too long​

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

error: use of undeclared identifier 'DefaultDelegateCheckMode'​

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.

Build Scripts Hang Until Keypress​

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.