[docs] Use a concrete example for --ninja-executable
Bug: 1411549
Change-Id: I13532a53ba35614c6c43f98365631a8a6bdd76d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4210771
Auto-Submit: Junji Watanabe <[email protected]>
Commit-Queue: Takuto Ikuta <[email protected]>
Reviewed-by: Takuto Ikuta <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1099649}
diff --git a/docs/windows_build_instructions.md b/docs/windows_build_instructions.md
index 3783c0b..e07b5ee 100644
--- a/docs/windows_build_instructions.md
+++ b/docs/windows_build_instructions.md
@@ -425,10 +425,11 @@
If you want to use Visual Studio Intellisense when developing Chromium, use the
`--ide` command line argument to `gn gen` when you generate your output
directory (as described on the [get the code](https://dev.chromium.org/developers/how-tos/get-the-code)
-page):
+page). This is an example when your checkout is `C:\src\chromium` and your
+output directory is `out\Default`:
```shell
-$ gn gen --ide=vs --ninja-executable=\path\to\chromium\src\third_party\ninja\ninja.exe out\Default
+$ gn gen --ide=vs --ninja-executable=C:\src\chromium\src\third_party\ninja\ninja.exe out\Default
$ devenv out\Default\all.sln
```
@@ -447,7 +448,7 @@
is:
```
-$ gn gen --ide=vs --ninja-executable=\path\to\chromium\src\third_party\ninja\ninja.exe --filters=//chrome --no-deps out\Default
+$ gn gen --ide=vs --ninja-executable=C:\src\chromium\src\third_party\ninja\ninja.exe --filters=//chrome --no-deps out\Default
```
You can selectively add other directories you care about to the filter like so:
