Consider a long makefile
with numerous targets, all of which are PHONY (meaning that the target name does not represent an existing file).
I can do either:<
If really all targets are PHONY, this is a bit pointless. make
is meant for "do what is necessary to update my output", and if the answer to what is necessary? is always the same, simple scripts would do the same job with less overhead.
That being said, I could imagine a situation where all targets intended to be given at the commandline should be PHONY -- Let's assume you want to build some documents like this:
all: doc1.pdf doc2.pdf doc3.pdf doc4.pdf doc5.pdf
manuals: doc3.pdf doc4.pdf
faqs: doc1.pdf
designdocs: doc2.pdf
apidocs: doc5.pdf
developerdocs: doc2.pdf doc5.pdf
userdocs: doc1.pdf doc3.pdf doc4.pdf
%.pdf: %.md
$(somedocgenerator) -o $@ $<
Then you could do the following:
.PHONY: all $(MAKECMDGOALS)
This would dynamically make any target given at the command line PHONY. Note you have to include your default target here as this could be invoked without giving it explicitly, by simply typing make
.
I would not recommend this approach because it has two drawbacks:
make
.make
a specific output file like here make doc3.pdf
.So, better go with the approach to have one line declaring all the PHONY targets. If your Makefile
is really huge, you could split it in several files and use include
-- and have one .PHONY:
line in each file.
One way to do it:
.PHONY: $(shell sed -n -e '/^$$/ { n ; /^[^ .\#][^ ]*:/ { s/:.*$$// ; p ; } ; }' $(MAKEFILE_LIST))
Works perfectly even for targets mentioned as dependencies.