| Index: docs/clang_tool_refactoring.md
|
| diff --git a/docs/clang_tool_refactoring.md b/docs/clang_tool_refactoring.md
|
| index 455464693391e406e67c078d0e32fcb3c840760d..4168145e19e9b2331583d2a45f9a0fce32a95884 100644
|
| --- a/docs/clang_tool_refactoring.md
|
| +++ b/docs/clang_tool_refactoring.md
|
| @@ -110,6 +110,12 @@ subdirectories in
|
| It is important to use --bootstrap as there appear to be [bugs](https://crbug.com/580745)
|
| in the clang library this script produces if you build it with gcc, which is the default.
|
|
|
| +Once clang is bootsrapped, incremental builds can be done by invoking `ninja` in
|
| +the `third_party/llvm-build/Release+Asserts` directory. In particular,
|
| +recompiling solely the tool you are writing can be accomplished by executing
|
| +`ninja rewrite_to_chrome_style` (replace `rewrite_to_chrome_style` with your
|
| +tool's name).
|
| +
|
| ## Running
|
| First, build all Chromium targets to avoid failures due to missing dependencies
|
| that are generated as part of the build:
|
|
|