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
I was trying to set up clang-tidy for a new repository. I was really struggling to get the compilation database to work and tried so many combinations of things, until I got it up amd running.
The particular issue was I was passing the path to the compile_commands.json file, as opposed to the path to the containing directory. It's clearly set out in the documentation, but it would have saved me a ton of time, if there was an option to turn on debug logs and see what's happening.
Wondering, if that's an easy thing to add for clang-tidy and the other tools in general?
The text was updated successfully, but these errors were encountered:
I was trying to set up clang-tidy for a new repository. I was really struggling to get the compilation database to work and tried so many combinations of things, until I got it up amd running.
The particular issue was I was passing the path to the compile_commands.json file, as opposed to the path to the containing directory. It's clearly set out in the documentation, but it would have saved me a ton of time, if there was an option to turn on debug logs and see what's happening.
Wondering, if that's an easy thing to add for clang-tidy and the other tools in general?
The text was updated successfully, but these errors were encountered: