本文解释了一种使用Doxygen解析来删除#include的技术。这只是一个perl脚本，所以它很容易使用。

这不是自动的，但是doxygen会为#included文件生成依赖关系图。你必须从视觉上看它们，但它们对于了解什么在使用什么是非常有用的。

CScout重构浏览器可以检测C(不幸的是不是c++)代码中多余的include指令。你可以在这篇期刊文章中找到它如何工作的描述。

您可以编写一个快速脚本，删除单个#include指令，编译项目，并在没有发生编译错误的情况下记录#include中的名称和它被删除的文件。

让它在晚上运行，第二天你就会有一个100%正确的可以删除的包含文件列表。

有时候蛮力很管用:-)

编辑:有时它不会:-)。下面是一些来自评论的信息:

Sometimes you can remove two header files separately, but not both together. A solution is to remove the header files during the run and not bring them back. This will find a list of files you can safely remove, although there might a solution with more files to remove which this algorithm won't find. (it's a greedy search over the space of include files to remove. It will only find a local maximum) There may be subtle changes in behavior if you have some macros redefined differently depending on some #ifdefs. I think these are very rare cases, and the Unit Tests which are part of the build should catch these changes.

The problem with detecting superfluous includes is that it can't be just a type dependency checker. A superfluous include is a file which provides nothing of value to the compilation and does not alter another item which other files depend. There are many ways a header file can alter a compile, say by defining a constant, redefining and/or deleting a used macro, adding a namespace which alters the lookup of a name some way down the line. In order to detect items like the namespace you need much more than a preprocessor, you in fact almost need a full compiler.

Lint更多的是一个样式检查器，当然不会有这个完整的功能。

我想你会发现检测多余include的唯一方法是删除、编译和运行套件。

我认为PCLint可以做到这一点，但我已经有几年没有研究它了。你可以去看看。

我看了这个博客，作者谈到了一些关于配置PCLint以查找未使用的包含的内容。也许值得一看。