Scripts to help building Electron
Перейти к файлу
Cheng 3c295c5eb3 Update build_chromium 2024-04-11 14:02:01 +09:00
vendor Update build_chromium 2024-04-11 14:02:01 +09:00
.gclient Scripts for building Electron 2018-10-01 16:12:40 +09:00
.gclient_rename_for_chromium Add .gclient file for chromium checkout 2023-10-25 13:29:59 +09:00
.gitignore Support building with reclient 2024-01-29 16:33:35 +09:00
.gitmodules Support building with reclient 2024-01-29 16:33:35 +09:00
README.md Move common.js out 2019-04-26 10:57:52 +09:00
bootstrap.js Support building with reclient 2024-01-29 16:33:35 +09:00
build.js Fix setting build target 2024-02-07 15:31:06 +09:00
common.js Add ninja to PATH 2023-02-01 20:31:20 +09:00
gn_gen.js Support building with reclient 2024-01-29 16:33:35 +09:00
test.js There is once one test now 2023-02-17 19:07:16 +09:00

README.md

be

Scripts to help building Electron.

(I'm still exploring what's the best way, hold on using this.)

Usage

Bootstrap:

./bootstrap.js [--skip-gclient] [--no-history] [--force] [--args=""] [--target-cpu=x64] [--verbose]

Build:

./build.js [configuration] [--verbose]

Run tests:

./test.js [configuration] [--force-install-modules] [-arbitrary-args-passed-to-spec...]

Configuration names

This project uses following convention for configuration names.

  • Default maps to electron/build/args/testing.gn.
  • Release maps to electron/build/args/release.gn.
  • Debug maps to electron/build/args/debug.gn.
  • For x64 target, there is no suffix to configuration name.
  • For other targets, the configuration name has _ and target name as suffix, for example Default_x86.

Development conventions

  • No package.json or npm install.

License

Public domain.