mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

docs: update the build docs for electron to improve doc readability (#32663)

Browse source
This commit is contained in:
Harshil jain 2022-01-31 17:06:47 +05:30 • committed by GitHub
parent c6d061c2d4
commit 32ae67c873
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 16 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

37
docs/development/build-instructions-gn.md
View file

@ -98,42 +98,37 @@ $ gclient sync -f
## Building ## Building
**Set the environment variable for chromium build tools**
On Linux & MacOS
```sh ```sh
$ cd src $ cd src
$ export CHROMIUM_BUILDTOOLS_PATH=`pwd`/buildtools $ export CHROMIUM_BUILDTOOLS_PATH=`pwd`/buildtools
$ gn gen out/Testing --args="import(\"//electron/build/args/testing.gn\") $GN_EXTRA_ARGS"
``` ```
Or on Windows (without the optional argument): On Windows:
```sh ```sh
$ cd src $ cd src
$ set CHROMIUM_BUILDTOOLS_PATH=%cd%\buildtools $ set CHROMIUM_BUILDTOOLS_PATH=%cd%\buildtools
```
**To generate Testing build config of Electron:**
```sh
$ gn gen out/Testing --args="import(\"//electron/build/args/testing.gn\")" $ gn gen out/Testing --args="import(\"//electron/build/args/testing.gn\")"
``` ```
This will generate a build directory `out/Testing` under `src/` with **To generate Release build config of Electron:**
the testing build configuration. You can replace `Testing` with another name,
but it should be a subdirectory of `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.
To see the list of available build configuration options, run `gn args
out/Testing --list`.
**For generating Testing build config of
Electron:**
```sh ```sh
$ gn gen out/Testing --args="import(\"//electron/build/args/testing.gn\") $GN_EXTRA_ARGS" $ gn gen out/Release --args="import(\"//electron/build/args/release.gn\")"
``` ```
**For generating Release (aka "non-component" or "static") build config of **Note:** This will generate a `out/Testing` or `out/Release` build directory under `src/` with the testing or release build depending upon the configuration passed above. You can replace `Testing|Release` with another names, but it should be a subdirectory of `out`.
Electron:**
```sh 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. To see the list of available build configuration options, run `gn args out/Testing --list`.
$ gn gen out/Release --args="import(\"//electron/build/args/release.gn\") $GN_EXTRA_ARGS"
```
**To build, run `ninja` with the `electron` target:** **To build, run `ninja` with the `electron` target:**
Note: This will also take a while and probably heat up your lap. Note: This will also take a while and probably heat up your lap.
@ -169,13 +164,13 @@ $ ./out/Testing/electron
On linux, first strip the debugging and symbol information: On linux, first strip the debugging and symbol information:
```sh ```sh
electron/script/strip-binaries.py -d out/Release $ electron/script/strip-binaries.py -d out/Release
``` ```
To package the electron build as a distributable zip file: To package the electron build as a distributable zip file:
```sh ```sh
ninja -C out/Release electron:electron_dist_zip $ ninja -C out/Release electron:electron_dist_zip
``` ```
### Cross-compiling ### Cross-compiling