Call out commands to be run to install depot_tools
Other mandatory command steps are called out using <pre> blocks. This makes to more obvious that running gclient after unpacking depot_tools.zip is a mandatory step. Bug: 1259839 Change-Id: I7a8eb512b7f59697d411da0e481fafac00faaae6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3230403 Auto-Submit: Reilly Grant <reillyg@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Reviewed-by: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/main@{#933124}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
5deec4721d
commit
07ff22e84b
@ -95,9 +95,14 @@ installation path of Visual Studio 2017 or 19, like
|
||||
`set vs2019_install=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional`
|
||||
for Visual Studio 2019.
|
||||
|
||||
From a cmd.exe shell, run the command gclient (without arguments). On first
|
||||
run, gclient will install all the Windows-specific bits needed to work with
|
||||
the code, including msysgit and python.
|
||||
From a cmd.exe shell, run:
|
||||
|
||||
```shell
|
||||
$ gclient
|
||||
```
|
||||
|
||||
On first run, gclient will install all the Windows-specific bits needed to work
|
||||
with the code, including msysgit and python.
|
||||
|
||||
* If you run gclient from a non-cmd shell (e.g., cygwin, PowerShell),
|
||||
it may appear to run properly, but msysgit, python, and other tools
|
||||
|
Reference in New Issue
Block a user