yvvan added a comment. In https://reviews.llvm.org/D49794#1182272, @ilya-biryukov wrote:
> In https://reviews.llvm.org/D49794#1182220, @yvvan wrote: > > > And we already saw, that -isystem is not the best choice for that. > > > Are you referring to the file-locking on Windows? > Any other reasons why the -isystem trick might be non-ideal? File locking is the first one. Another one comes with "plugin mode" of tidy. >> And by the way - clang-tidy has this filtering in consumer which does not >> exist in it's plugin-mode so it spits all system diagnostics all the time... > > I would still argue against adding this option in the current form to the > compiler. I don't see how that might be useful to non-clang-tidy, > non-editor-integration users. > > What's the 'plugin mode' of clang-tidy? I don't seem to able to Google it :-) Clang tidy is not only a standalone tool but also a plugin. It's almost never used this way (but we do that in Qt Creator to combine it with Clazy) and it also seems that some of the recent checks are added only to standalone tool (which is easy to fix). Being loaded into clang as plugin it does not support most of clang-tidy command line options and is not able to filter system includes. I'm not sure it's possible to fix both of these issues (and probably some other). https://reviews.llvm.org/D49794 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
