chromium/src
0
Fork 0
Code Activity

[docs/clang-tidy] Mention script to build tools with correct revision

Browse Source 
Mention tools/clang/scripts/build_clang_tools_extra.py, which is an
easy way to build clang-tidy and clang-apply-replacements with the
the correct LLVM revision. This is what allowed me to write
crrev.com/c/3646293

Bug: None
Change-Id: Ibd4e48312a19acfb974228d41657da5addeae166
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3644796
Reviewed-by: Hans Wennborg <hans@chromium.org>
Auto-Submit: Victor Vianna <victorvianna@google.com>
Commit-Queue: Victor Vianna <victorvianna@google.com>
Cr-Commit-Position: refs/heads/main@{#1004163}
This commit is contained in:
Victor Vianna
2022-05-17 09:04:35 +00:00
committed by Chromium LUCI CQ
parent 5bc1988e70
commit 795669a9c7
1 changed files with 6 additions and 2 deletions

8
docs/clang_tidy.md

@ -208,8 +208,12 @@ your `$PATH`. However, the system packaged binaries might be several versions
behind Chromium's toolchain, so not all flags are guaranteed to work. If this is behind Chromium's toolchain, so not all flags are guaranteed to work. If this is
a problem, consider building clang-tidy from the same revision the current a problem, consider building clang-tidy from the same revision the current
toolchain is using, rather than filing a bug against the toolchain component. toolchain is using, rather than filing a bug against the toolchain component.
This can be done as follows:
Running clang-tidy is (hopefully) simple. ```
tools/clang/scripts/build_clang_tools_extra.py \
--fetch out/Release clang-tidy clang-apply-replacements
```
Running clang-tidy is then (hopefully) simple.
1. Build chrome normally. 1. Build chrome normally.
``` ```
ninja -C out/Release chrome ninja -C out/Release chrome