The Cactus build process auto-generates some glue code in bindings which clutters the coverage analysis. Similarly ExternalLibraries contain code that we don't ourself maintain.
I may be useful not to include these codes in the coverage analysis.
The attached patch does so by inspecting the directory to be processed when generating the results page.
Is this a desirable feature and an implementation that is acceptable?