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 Aug 7, 2023. It is now read-only.
So, the README and the Changelog talk about compile_commands.json support. Is it true or is it missing ?
I don't know why, but linter-clang seems to ignore my compile_commands.json. It reports missing header errors but when I test my file with clang-check -analyze <file> it reports no error.
It was a problem on my side. I use a symlink from my sources to my build workspace, so the sources seen by CMake were on a different location than the ones seen by linter-clang.
The compile_commands.json works fine. Mybe this issue should be closed ?
If I understand @samuela right, a config option is requested to set a path, where to search for compile_commands.json.
For myself I use a subdirectory for CMake build files and the compile_commands.json is also written into this directory. However, telling the linter to search in $PROJECT_ROOT/build/ for this file would make a symlink for this file in each project's root superfluous.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AFAICT, there's no way to point linter-clang to a
compile_commands.json
file. How exactly is this supposed to work?The text was updated successfully, but these errors were encountered: