还可以查看include-what-you-use，它可以解决类似的问题。

有一个免费的工具包括文件依赖监视器，它可以集成到可视化工作室中。它用红色显示多余的#include。

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

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

有两种类型的多余的#include文件:

头文件实际上不需要 模块(.c， .cpp) 模块需要头文件 而是不止一次，直接或间接地。

根据我的经验，有两种方法可以很好地检测到它:

gcc -H or cl.exe /showincludes (resolve problem 2) In real world, you can export CFLAGS=-H before make, if all the Makefile's not override CFLAGS options. Or as I used, you can create a cc/g++ wrapper to add -H options forcibly to each invoke of $(CC) and $(CXX). and prepend the wrapper's directory to $PATH variable, then your make will all uses you wrapper command instead. Of course your wrapper should invoke the real gcc compiler. This tricks need to change if your Makefile uses gcc directly. instead of $(CC) or $(CXX) or by implied rules. You can also compile a single file by tweaking with the command line. But if you want to clean headers for the whole project. You can capture all the output by: make clean make 2>&1 | tee result.txt PC-Lint/FlexeLint(resolve problem both 1 and 2) make sure add the +e766 options, this warning is about: unused header files. pclint/flint -vf ... This will cause pclint output included header files, nested header files will be indented appropriately.

这里有一个简单的暴力方法来识别多余的头包含。它并不完美，但消除了“明显的”不必要的包含。清除这些代码对清理代码大有帮助。

这些脚本可以直接在GitHub上访问。

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的唯一方法是删除、编译和运行套件。