You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When integrating this tool off-the-shelf with our build system, it has a curious problem: it tries to run clang-tidy for each of the #include-d files from our system. We do have an exclude filter in the clang tidy config itself, but that applies after clang-tidy itself runs. As a result, clang-tidy runs tens of thousands of times (once for each #include), which breaks the system.
To get around this, I added a (admittedly hacky) company-specific inclusion logic (see this PR). It works, but it's not very elegant.
Could you consider adding some kind of mechanism for the user to specify inclusion/exclusion criteria for source files? I'm exploring how to configure an aspect; if I write a PR that adds some kind of clang_tidy_source_must_include_substring option, are you amenable to adding that to the repo?
The text was updated successfully, but these errors were encountered:
When integrating this tool off-the-shelf with our build system, it has a curious problem: it tries to run clang-tidy for each of the #include-d files from our system. We do have an exclude filter in the clang tidy config itself, but that applies after clang-tidy itself runs. As a result, clang-tidy runs tens of thousands of times (once for each #include), which breaks the system.
To get around this, I added a (admittedly hacky) company-specific inclusion logic (see this PR). It works, but it's not very elegant.
Could you consider adding some kind of mechanism for the user to specify inclusion/exclusion criteria for source files? I'm exploring how to configure an
aspect
; if I write a PR that adds some kind ofclang_tidy_source_must_include_substring
option, are you amenable to adding that to the repo?The text was updated successfully, but these errors were encountered: