Phony | search
Click here to view Phony news from 60+ newspapers.
Bookmark or Share- What is the purpose of .PHONY in a Makefile? - Stack OverflowPHONY forces a label/file in a Makefile to be built if it's part of the topological-sort of whatever your target is. That is to say, if you have a 'cleanup:' label that is set phony, and the your install label is defined with cleanup as a prerequisite - i.e. 'install: cleanup', cleanup will always be run when the Makefile attempts to build ...
- Is it possible to have multiple .PHONY targets in a GNU makefile?Yes, a common pattern is to have a PHONY right above the relevant target. Can also have multi-line phonies by ending the continuing line with \ Can also have multi-line phonies by ending the continuing line with \
- Makefile : .PHONY on multiple targets - Stack OverflowBut if you are willing to depend specifically on GNU make (which your references to .PHONY and % suggest) then you can do at least a little better than what is described in the question. For example, define a variable containing the varying stems of your target names, and expand that to a list of prerequisites for .PHONY:
- make implicit rule with force vs .phony - Stack OverflowSince it knows that phony targets do not name actual files that could be remade from other files, make skips the implicit rule search for phony targets. In your case I would just use explicit rule, may be with a static pattern:.PHONY: $(addprefix $(tsdir)/, $(projects)) $(addprefix $(tsdir)/, $(projects)) : $(tsdir)/% : make -C $(prereqdir)/$*
- Real targets with PHONY dependencies - Stack Overflow.PHONY: FOO FOO: foo foo: build foo .PHONY: BAR BAR: bar bar: FOO build bar The idea here is that I want to abstract the real files (foo, bar) with phony targets (FOO BAR). In my real Makefile, of course, it is more complicated which is why the abstraction is important.
More
