From c30a6232df03e1efbd9f3b226777b07e087a1122 Mon Sep 17 00:00:00 2001 From: Allan Sandfeld Jensen Date: Mon, 12 Oct 2020 14:27:29 +0200 Subject: BASELINE: Update Chromium to 85.0.4183.140 Change-Id: Iaa42f4680837c57725b1344f108c0196741f6057 Reviewed-by: Allan Sandfeld Jensen --- chromium/docs/clangd.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) (limited to 'chromium/docs/clangd.md') diff --git a/chromium/docs/clangd.md b/chromium/docs/clangd.md index 99559663c4a..a289997a195 100644 --- a/chromium/docs/clangd.md +++ b/chromium/docs/clangd.md @@ -13,8 +13,14 @@ See [instructions](https://clang.llvm.org/extra/clangd/Installation.html#install **Googlers:** clangd has been installed on your glinux by default, just use `/usr/bin/clangd`. -Alternative: use the following command to build clangd from LLVM source, and you -will get the binary at +Alternative: download clangd from the official [Releases](https://github.com/clangd/clangd/releases) +page. + +Note: clangd 10.0.0 does not work with Chromium; use one of the pre-release +versions lower down on the Releases page until a newer version is released. + +If you prefer to build clangd locally, use the following command to build from +LLVM source, and you will get the binary at `out/Release/tools/clang/third_party/llvm/build/bin/clangd`. ``` @@ -36,8 +42,9 @@ source file. 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. +Note: the compilation database is not regenerated automatically. You need to +regenerate it manually whenever build rules change, e.g., when you have new files +checked in or when you sync to head. If using Windows PowerShell, use the following command instead to set the output's encoding to UTF-8 (otherwise Clangd will hit "YAML:1:4: error: Got -- cgit v1.2.1