Configuring team's compile commands location

[SebastianBilek]

Hey there, I'm looking for team-friendly way to give cpptools the location of compile_commands.json, given that our compile commands is located in the git ignored ./work subdirectory of our projects.

During a dev call we explored the following options:

• Setting the global C_Cpp.default.compileCommands to ./work/compile_commands.json works great. However, devs felt that the solution is not scalable or easy to automate as a all devs have to manually configure the option and we already had a dev fail to configure it during the call 😆
• Configuring compileCommands setting inside the local .vscode/c_cpp_properties.json file frustrated a few people during the call as they didn't want to have to share any vscode configurations and were concerned that just adding the .vscode subdirectory to the repos would lead to a creep of configuration options.
• Finally, for clangd you can symlink the compile_commands.json into ./build and although this isn't supported by cpptools the idea was very popular during the call as it wouldn't be adding anything to the root of the repos, wouldn't intefere with people's vscode configuration, might support more editors (that use clangd), and is automatic (like using c_cpp_properties.json).

Which of these options are recommended? Are there other strategies we should consider? Also, is there a possibility for cpptools to support default search directories for compile commands?

Thanks!