Make clean删除所有已编译的目标文件。

根据米勒的递归使认为有害，你应该避免调用$(Make)!在您所展示的情况中，它是无害的，因为这不是一个真正的makefile，只是一个包装器脚本，它也可能是用Shell编写的。但是你说你在更深层次的递归中继续这样做，所以你可能遇到了那篇令人大开眼界的文章中所显示的问题。

当然，使用GNU的make是很麻烦的。尽管他们意识到了这个问题，但这是他们记录在案的做事方式。

OTOH，创建makepp就是为了解决这个问题。您可以在每个目录级别上编写makefile文件，但它们都汇集到项目的完整视图中。

But legacy makefiles are written recursively. So there's a workaround where $(MAKE) does nothing but channel the subrequests back to the main makepp process. Only if you do redundant or, worse, contradictory things between your submakes, you must request --traditional-recursive-make (which of course breaks this advantage of makepp). I don't know your other makefiles, but if they're cleanly written, with makepp necessary rebuilds should happen automatically, without the need for any hacks suggested here by others.

make的-B开关，其长形式为——always-make，告诉make忽略时间戳并使指定的目标。这可能会违背使用make的目的，但它可能正是您所需要的。

这种简单的技术将允许makefile在不需要强制时正常运行。在makefile的末尾创建一个名为force的新目标。强制目标将触及默认目标所依赖的文件。在下面的例子中，我添加了touch myprogram.cpp。我还添加了一个要做的递归调用。这将导致每次输入make force时都会生成默认目标。

yourProgram: yourProgram.cpp
       g++ -o yourProgram yourProgram.cpp 

force:
       touch yourProgram.cpp
       make

你可以宣布一个或多个目标是假的。

A phony target is one that is not really the name of a file; rather it is just a name for a recipe to be executed when you make an explicit request. There are two reasons to use a phony target: to avoid a conflict with a file of the same name, and to improve performance. ... A phony target should not be a prerequisite of a real target file; if it is, its recipe will be run every time make goes to update that file. As long as a phony target is never a prerequisite of a real target, the phony target recipe will be executed only when the phony target is a specified goal

如果您不需要保存已经成功编译的任何输出

nmake /A 

重建所有