Adjusting Windows build docs for symbol_level changes
Change-Id: I18b2224264abdda5edce714f303ece788f15514a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2176520
Commit-Queue: Bruce Dawson <[email protected]>
Commit-Queue: Sébastien Marchand <[email protected]>
Auto-Submit: Bruce Dawson <[email protected]>
Reviewed-by: Sébastien Marchand <[email protected]>
Cr-Commit-Position: refs/heads/master@{#764819}
diff --git a/docs/windows_build_instructions.md b/docs/windows_build_instructions.md
index 8845f848..1e66285 100644
--- a/docs/windows_build_instructions.md
+++ b/docs/windows_build_instructions.md
@@ -248,10 +248,13 @@
* `blink_symbol_level = 0` - turn off source-level debugging for
blink to reduce build times, appropriate if you don't plan to debug blink.
-In order to speed up linking you can set `symbol_level = 1` - this option
-reduces the work the linker has to do but when this option is set you cannot do
-source-level debugging. Switching from `symbol_level = 2` (the default) to
-`symbol_level = 1` requires recompiling everything.
+In order to speed up linking you can set `symbol_level = 1` or
+`symbol_level = 0` - these options reduce the work the compiler and linker have
+to do. With `symbol_level = 1` the compiler emits file name and line number
+information so you can still do source-level debugging but there will be no
+local variable or type information. With `symbol_level = 0` there is no
+source-level debugging but call stacks still have function names. Changing
+`symbol_level` requires recompiling everything.
In addition, Google employees should use goma, a distributed compilation system.
Detailed information is available internally but the relevant gn arg is:
