Instead of put a compile_commands.json at source root

[playgithub]

For cmake projects, compile_commands.json has to be copied/linked to the source root directory now.
Instead of this, can a property of vscode workspace be set, so that vscode-clangd knows where is compile_commands.json?

[HighCommander4]

Yes, this can be done today by adding the following to <project>/.vscode/settings.json:

{
  "clangd.arguments": [
    "--compile-commands-dir=<path_to_directory_containing_compile_commands.json>"
  ]
}

Another way is to use clangd's own config file (see the CompilationDatabase key in the docs).

[playgithub]

Yes, this can be done today by adding the following to <project>/.vscode/settings.json:

{
  "clangd.arguments": [
    "--compile-commands-dir=<path_to_directory_containing_compile_commands.json>"
  ]
}

That's it, thanks.

Another way is to use clangd's own config file (see the CompilationDatabase key in the docs).

It doesn't seem workspace specific, does it?

[HighCommander4]

Another way is to use clangd's own config file (see the CompilationDatabase key in the docs).

It doesn't seem workspace specific, does it?

It can be. From the docs:

• project configuration: a file named .clangd in the source tree. (clangd searches in all parent directories of the active file).

[i-ky]

@playgithub, if you use CMake Tools extension, then there is a cmake.copyCompileCommands setting that tells CMake Tools to copy compilation database from build directory to a desired location (e.g. ${workspaceFolder}). This will work even if you have different build directories depending on build configuration and whatnot. --compile-commands-dir and CompilationDatabase will only allow one possible location.

[playgithub]

@playgithub, if you use CMake Tools extension, then there is a cmake.copyCompileCommands setting that tells CMake Tools to copy compilation database from build directory to a desired location (e.g. ${workspaceFolder}). This will work even if you have different build directories depending on build configuration and whatnot. --compile-commands-dir and CompilationDatabase will only allow one possible location.

Anyway it's an assistant file, I prefer to make it transparent.