o.gyorgy added a comment. In https://reviews.llvm.org/D24040#530546, @mehdi_amini wrote:
> > This looks like a fairly large tool. Should it get its own "subproject > > level" directory in the SVN instead of being nested within clang? > > > I'd add that the clang-tools-extra are more closely tied to clang than what > this seems to be. Is there a strong rev-lock with clang that I missed? I've put it here because it is similar to scan-build/scan-build-py and on OSX it uses the intercept-build from scan-build-py. Right now there is an alternative logger on linux (not in this patch) but we plan to move to use only the intercept-build. We process the output generated by clang and clang-tidy and we use the command line options for these tools which could change with newer revisions, in that case this tool needs to be updated too. I will update the readme too. https://reviews.llvm.org/D24040 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
