@@ -24,36 +24,23 @@ try to download a Google-internal version that only Googlers have access to).
24
24
25
25
[ depot-tools ] : http://commondatastorage.googleapis.com/chrome-infra-docs/flat/depot_tools/docs/html/depot_tools_tutorial.html#_setting_up
26
26
27
- ## Cached builds (optional step)
27
+ ### Setting up the git cache
28
28
29
- ### GIT\_ CACHE\_ PATH
30
-
31
- If you plan on building Electron more than once, adding a git cache will
32
- speed up subsequent calls to ` gclient ` . To do this, set a ` GIT_CACHE_PATH `
33
- environment variable:
29
+ If you plan on checking out Electron more than once (for example, to have
30
+ multiple parallel directories checked out to different branches), using the git
31
+ cache will speed up subsequent calls to ` gclient ` . To do this, set a
32
+ ` GIT_CACHE_PATH ` environment variable:
34
33
35
34
``` sh
36
35
$ export GIT_CACHE_PATH=" ${HOME} /.git_cache"
37
36
$ mkdir -p " ${GIT_CACHE_PATH} "
38
37
# This will use about 16G.
39
38
```
40
39
41
- ### sccache
42
-
43
- Thousands of files must be compiled to build Chromium and Electron.
44
- You can avoid much of the wait by reusing Electron CI's build output via
45
- [ sccache] ( https://github.com/mozilla/sccache ) . This requires some
46
- optional steps (listed below) and these two environment variables:
47
-
48
- ``` sh
49
- export SCCACHE_BUCKET=" electronjs-sccache-ci"
50
- export SCCACHE_TWO_TIER=true
51
- ```
52
-
53
40
## Getting the code
54
41
55
42
``` sh
56
- $ mkdir electron-gn && cd electron-gn
43
+ $ mkdir electron && cd electron
57
44
$ gclient config --name " src/electron" --unmanaged https://github.com/electron/electron
58
45
$ gclient sync --with_branch_heads --with_tags
59
46
# This will take a while, go get a coffee.
0 commit comments