构建说明

    各个平台所对应的构建要求如下：

    构建工具

    Electron的构建工具 自动化了很多配置不同的从源代码编译Electron的设置和构建目标。 如果您希望手动设置环境，则说明如下。

    此外，你还需要安装，这是一个用于获取Chromium，及其相关依赖工具。

    另外，如果使用Windows系统, 你需要设置环境变量。 依次打开 Control Panel → System and Security → System → Advanced system settings ，然后添加系统变量 DEPOT_TOOLS_WIN_TOOLCHAIN ，并设置默认值为 0. 这将促使depot_tools 使用本地已安装的Visual Studio(默认状态下，depot_tools将会下载一个只有谷歌内部员工有权限使用的内部版本)。

    如果您想 checkout 多份 Electron 源码 (例如多个并行目录 checkout 到不同的分支)， 推荐使用 git 缓存来加速后续对 gclient的调用。 为此，设置 GIT_CACHE_PATH 环境变量：

    获取代码

    1. $ gclient config --name "src/electron" --unmanaged https://github.com/electron/electron
    2. $ gclient sync --with_branch_heads --with_tags
    3. # 这将需要一段时间，喝杯咖啡休息一下。

    拉/推的注意事项

    如果您将来打算从 electron 官方地址进行 git pull 或 git push，那么您需要更新相应文件夹的源 URL。

    1. $ cd src/electron
    2. $ git remote remove origin
    3. $ git remote add origin https://github.com/electron/electron
    4. $ git checkout main
    5. $ git branch --set-upstream-to=origin/main
    6. $ cd -

    📝 gclient 会检查 src/electron 目录下的 DEPS 文件，从中获取依赖信息 (就像 Chromium 或 Node.js 那样)。 运行 gclient sync -f 确保所有用来构建 Electron 的依赖都符合该文件的描述。

    因此，为了拉取，您将运行以下命令：

    1. $ cd src/electron
    2. $ git pull
    1. $ cd src
    2. $ export CHROMIUM_BUILDTOOLS_PATH=`pwd`/buildtools
    3. $ gn gen out/Testing --args="import(\"//electron/build/args/testing.gn\") $GN_EXTRA_ARGS"

    若在 Windows 上 (没有可选参数)：

    1. $ cd src
    2. $ set CHROMIUM_BUILDTOOLS_PATH=%cd%\buildtools
    3. $ gn out/testing --args="import(\"//electron/build/args/testing.gn\")

    这将在src/下的out/Testing内生成一个有测试生成配置的文件夹 您可以用另一个名称 替换 Testing ，但它应该是 out 的子目录。 Also you shouldn’t have to run gn gen again—if you want to change the build arguments, you can run gn args out/Testing to bring up an editor.

    要查看可用的构建配置选项的列表，运行 gn args out/Testing--list。

      For generating Release (aka “non-component” or “static”) build config of Electron:

      To build, run ninja with the electron target: Nota Bene: This will also take a while and probably heat up your lap.

      测试配置：

      1. $ ninja -C out/Testing electron

      发布配置：

      1. $ ninja -C out/Release electron

      This will build all of what was previously ‘libchromiumcontent’ (i.e. the content/ directory of chromium and its dependencies, incl. WebKit and V8), so it will take a while.

      构建需要在./out/Testing文件下执行：

      1. $ ./out/Testing/Electron.app/Contents/MacOS/Electron
      2. # or, on Windows
      3. $ ./out/Testing/electron.exe
      4. # or, on Linux
      5. $ ./out/Testing/electron

      On linux, first strip the debugging and symbol information:

      1. electron/script/strip-binaries.py -d out/Release

      To package the electron build as a distributable zip file:

      1. ninja -C out/Release electron:electron_dist_zip

      交叉编译

      To compile for a platform that isn’t the same as the one you’re building on, set the target_cpu and target_os GN arguments. For example, to compile an x86 target from an x64 host, specify target_cpu = "x86" in .

      1. $ gn gen out/Testing-x86 --args='... target_cpu = "x86"'

      Not all combinations of source and target CPU/OS are supported by Chromium.

      If you test other combinations and find them to work, please update this document :)

      有关 和 target_cpu 的有效值，请查看参考 GN。

      Windows on Arm (experimental)

      Or (if using PowerShell):

      1. $env:ELECTRON_BUILDING_WOA=1
      2. gclient sync -f --with_branch_heads --with_tags

      Next, run gn gen as above with target_cpu="arm64".

      测试

      To run the tests, you’ll first need to build the test modules against the same version of Node.js that was built as part of the build process. To generate build headers for the modules to compile against, run the following under src/ directory.

      1. $ ninja -C out/Testing third_party/electron_node:headers

      You can now .

      可以通过增加其它标记来调试程序，例如：

      1. $ npm run test -- \
      2.   --enable-logging -g 'BrowserWindow module'

      可以将gclient git 缓存与其他机器共享，导出为 SMB 在linux上共享。 但每次只能有一个进程或机器可以使用缓存。 The locks created by git-cache script will try to prevent this, but it may not work perfectly in a network.

      On Windows, SMBv2 has a directory cache that will cause problems with the git cache script, so it is necessary to disable it by setting the registry key

      1. HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanworkstation\Parameters\DirectoryCacheLifetime

      to 0. 更多信息：https://stackoverflow.com/a/9935126

      This can be set quickly in powershell (ran as administrator):

      1. New-ItemProperty -Path "HKLM:\System\CurrentControlSet\Services\Lanmanworkstation\Parameters" -Name DirectoryCacheLifetime -Value 0 -PropertyType DWORD -Force

      故障排查

      If gclient sync is interrupted the git tree may be left in a bad state, leading to a cryptic message when running gclient sync in the future:

      1. 2> Conflict while rebasing this branch.
      2. 2> See man git-rebase for details.

      If there are no git conflicts or rebases in src/electron, you may need to abort a git am in src:

      I’m being asked for a username/password for chromium-internal.googlesource.com

      If you see a prompt for Username for 'https://chrome-internal.googlesource.com': when running gclient sync on Windows, it’s probably because the DEPOT_TOOLS_WIN_TOOLCHAIN environment variable is not set to 0. Open Control Panel → System and Security → System → Advanced system settings and add a system variable DEPOT_TOOLS_WIN_TOOLCHAIN with value 0. 这将促使depot_tools 使用本地已安装的Visual Studio(默认状态下，将会下载一个只有谷歌内部员工有权限使用的内部版本)。