clang-tidy relies on the compile_commands.json files outputted by cmake during compilation. Unfortunately, this means that
a) code must always be compiled before running clang-tidy
b) code that is not compiled (For example, files specific to real HW) are not analyzed
In addition, simply cross-compiling and then running the clang-tidy script causes the tool to get confused by the cross-compilation and report tons of irrelevant errors as well as misreporting true errors.
🐛 Bug Report
clang-tidy relies on the
compile_commands.jsonfiles outputted by cmake during compilation. Unfortunately, this means thata) code must always be compiled before running clang-tidy b) code that is not compiled (For example, files specific to real HW) are not analyzed
In addition, simply cross-compiling and then running the clang-tidy script causes the tool to get confused by the cross-compilation and report tons of irrelevant errors as well as misreporting true errors.