Bug 1829512 - Use .clangd rather than vscode-specific configuration to point...

Bug 1829512 - Use .clangd rather than vscode-specific configuration to point to the compilation database. r=andi

Differential Revision: https://phabricator.services.mozilla.com/D176230

.gitignore

@@ -35,6 +35,7 @@ ID
 
 # User files that may appear at the root
 /.clang-tidy
+/.clangd
 /.mozconfig*
 /mozconfig*
 /old-configure

.hgignore

@@ -33,6 +33,7 @@ compile_commands\.json
 
 # User files that may appear at the root
 ^\.clang-tidy
+^\.clangd
 ^\.mozconfig
 ^mozconfig*
 ^\.moz-fast-forward

python/mozbuild/mozbuild/backend/mach_commands.py

@@ -299,11 +299,18 @@ def setup_clangd_rust_in_vscode(command_context):
     with open(".clang-tidy", "w") as file:
         yaml.dump(clang_tidy, file)
 
+    clangd_cfg = {
+        "CompileFlags": {
+            "CompilationDatabase": clangd_cc_path,
+        }
+    }
+
+    with open(".clangd", "w") as file:
+        yaml.dump(clangd_cfg, file)
+
     return {
         "clangd.path": clangd_path,
         "clangd.arguments": [
-            "--compile-commands-dir",
-            clangd_cc_path,
             "-j",
             str(multiprocessing.cpu_count() // 2),
             "--limit-results",