Repository navigation
Warning about 'Failed to detect analyzer binary!' #3584
|
Hi all, I ran: CodeChecker analyze compile_commands.json -o ./reports and got something like this: [snip] I was able to run CodeChecker parse ./reports -e html -o ./reports_html after that and it seemed to generate a bunch of reports. However, I'm still not sure what the warning was about and if it affected the amount and quality of reports. The message itself is far from being helpful in debugging this as it not clear on what exactly failed and does not say exactly what to look for. Any thoughts? Nick |
Replies: 3 comments 1 reply
|
If you don't want to see this warning message you can enable only |
|
Ah, indeed. I built it clangsa from scratch and the warning has gone away. |
|
Just for future references: According to mentioned above instruction, it is required to build the clang from source, which is in fact not necessarily truth. In ubuntu CodeChecker launches |
CodeChecker analyzecommand by default will try to run both clang-tidy and clangsa analyzers. In your system it looks like you have installed onlyclang-tidyso CodeChecker will only run only this analyzer.If you don't want to see this warning message you can enable only
clang-tidyanalyzer (CodeChecker analyze --analyzers clang-tidy ...) or you can install clangsa analyzer (for more information about this see: https://clang-analyzer.llvm.org/).