You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2023. It is now read-only.
The clangd extension supports specifying a compile_commands.json file which specifies the compiler arguments that are used to build each source file. The system that vscode-clang-tidy uses of requiring the user to specify a single set of arguments for the whole project doesn't work for projects where the arguments vary from file to file, or directory to directory at least. Could compile_commands.json support be added at some point? :-)
The text was updated successfully, but these errors were encountered:
Seems like this is already supported: #40
I could verify using a full absolute path, couldn't get it to work with a path containing variables like ${workspaceFolder} or a relative path.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The clangd extension supports specifying a compile_commands.json file which specifies the compiler arguments that are used to build each source file. The system that vscode-clang-tidy uses of requiring the user to specify a single set of arguments for the whole project doesn't work for projects where the arguments vary from file to file, or directory to directory at least. Could compile_commands.json support be added at some point? :-)
The text was updated successfully, but these errors were encountered: