Oops, hit "Submit" early. So, I find this approach problematic for a couple of reasons:
1. lack of support for other compilation databases makes the feature hardly usable for many use cases (fixed compilation database is the most basic case which doesn't work well for real projects). 2. getting the list of plugins from the file's compiler arguments seems like a wrong approach. The list of available checks becomes dependent on the build configuration of the project. I think, a better approach is to add a clang-tidy option for loading a static analyzer plugin and feed it to the static analyzer. http://reviews.llvm.org/D9555 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
