xazax.hun added a comment. Guide to run the two pass analysis:
Process ------- These are the steps of XTU analysis: 1. `xtu-build.py` script uses your compilation database and extracts all necessary information from files compiled. It puts all its generated data into a folder (.xtu by default). 2. `xtu-analyze.py` script uses all previously generated data and executes the analysis. It needs the clang binary and scan-build-py's analyze-cc in order to do that. The output is put into a folder (.xtu-out by default) where both the analysis reports and the called commands' generated output are stored. Usage example ------------- 1. You have generated a compilation database and you are in your project's build directory 2. `xtu-build.py -b build.json -v --clang-path <path-to-folder-of-clang-binary>` 3. `xtu-analyse.py -b build.json -v --clang-path <path-to-folder-of-clang-binary> --analyze-cc-path <path-to-folder-of-analyze-cc-script>` Repository: rL LLVM https://reviews.llvm.org/D30691 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
