chromium/src
0
Fork 0
Code Activity

Recommend just a gn gen to setup the compile database.

Browse Source 
As far as I can tell, we only need the ninja files, not the full build.
Just refreshing the ninja files is considerably faster. (I may be
confused. Someone who knows for sure should review this.)

Bug: none
Change-Id: I17a963b00804b4f5db160cbd63b5ea836258f303
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590238
Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#657151}
This commit is contained in:
David Benjamin
2019-05-07 07:19:10 +00:00
committed by Commit Bot
parent 3a5ceb9f04
commit f676adb1af
1 changed files with 11 additions and 4 deletions

15
docs/clangd.md

@ -23,11 +23,10 @@ tools/clang/scripts/build_clang_tools_extra.py --fetch out/Release clangd
## Setting Up
1. Build chrome normally. This step is required to make sure we have all
generated files.
1. Make sure generated ninja files are up-to-date.
```
ninja -C out/Release chrome
gn gen out/Release
```
2. Generate the compilation database, clangd needs it to know how to build a
@ -40,7 +39,15 @@ tools/clang/scripts/generate_compdb.py -p out/Release > compile_commands.json
Note: the compilation database is not re-generated automatically, you'd need to
regenerate it manually when you have new files checked in.
3. Use clangd in your favourite editor, see detailed [instructions](
3. Optional: build chrome normally. This ensures generated headers exist and are
up-to-date. clangd will still work without this step, but it may give errors or
inaccurate results for files which depend on generated headers.
```
ninja -C out/Release chrome
```
4. Use clangd in your favourite editor, see detailed [instructions](
https://clang.llvm.org/extra/clangd/Installation.html#getting-started-with-clangd).
## Index