Skip to content

Commit c0a93c1

Browse files
jdoerrieChromium LUCI CQ
authored and
Chromium LUCI CQ
committed
[docs] Mention package manangers in docs/clang_tidy.md
Change-Id: I96db5f04b36fc9f9a066b46afb72d01469b1cedf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2764470 Commit-Queue: George Burgess <[email protected]> Reviewed-by: George Burgess <[email protected]> Cr-Commit-Position: refs/heads/master@{#871519}
1 parent 4d1729d commit c0a93c1

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

docs/clang_tidy.md

+9
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,15 @@ That said, assuming you have the LLVM sources available, you'll need to bring
197197
your own `clang-apply-replacements` binary if you want to use the `-fix` option
198198
noted below.
199199

200+
**Note:** If you're on a system that offers a clang tools through its package
201+
manager (e.g., on Debian/Ubuntu, `sudo apt-get install clang-tidy clang-tools`),
202+
you might not need an LLVM checkout to make the required binaries and scripts
203+
(`clang-tidy`, `run-clang-tidy` and `clang-apply-replacements`) available in
204+
your `$PATH`. However, the system packaged binaries might be several versions
205+
behind Chromium's toolchain, so not all flags are guaranteed to work. If this is
206+
a problem, consider building clang-tidy from the same revision the current
207+
toolchain is using, rather than filing a bug against the toolchain component.
208+
200209
Running clang-tidy is (hopefully) simple.
201210
1. Build chrome normally.
202211
```

0 commit comments

Comments
 (0)