You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -194,7 +194,7 @@ To see all potential options for this command, run:
194
194
$ e build --help
195
195
```
196
196
197
-
Once you have the source, the next step is to build it with `e build [target]`.
197
+
Once you have the source, the next step is to build it with `e build --target [target]`.
198
198
Some of the build targets you may want to build include:
199
199
200
200
| Target | Description |
@@ -248,6 +248,12 @@ For example, running `e d gn ls out/Testing | grep "//ui/views/"` produces somet
248
248
249
249
You could then run `e build --target ui/views/examples:views_examples_with_content` to produce Chrome's `//ui/views` example executable and run it with `./out/Testing/views_examples_with_content`.
250
250
251
+
When first run, `e build` will try to set up reclient to speed up your builds. The permission prompt
252
+
can look scary because GitHub's UI is less than optimal
253
+
([related discussion](https://github.com/orgs/community/discussions/37117)). However, Electron only
254
+
obtains user profile access and `read:org` permission. No permission is granted to any of your
0 commit comments