59528d9f0e
When using scan-build, you're often going to want to use it in the context of a Nix expression with buildInputs, and the default wrapper scripts will put things like include locations for those inputs $NIX_CFLAGS_COMPILE. Thus, scan-build also needs to pass them to the analyzer - while the link flags aren't relevant, the include flags are. This is because the analyzer executable that gets run by scan-build is *not* clang-wrapper, but the actual clang executable, so it doesn't implicitly add such arguments. The build is two-stage - it runs the real clang wrapper once, and then the analyzer once. Signed-off-by: Austin Seipp <aseipp@pobox.com> |
||
|---|---|---|
| .. | ||
| checkstyle | ||
| clang-analyzer | ||
| cov-build | ||
| cppcheck | ||
| emma | ||
| findbugs | ||
| frama-c | ||
| jdepend | ||
| lcov | ||
| pmd | ||
| radare | ||
| smatch | ||
| sparse | ||
| spin | ||
| splint | ||
| valgrind | ||
| valkyrie | ||