What is the purpose of .PHONY in a Makefile? - Stack Overflow
WEBJan 27, 2010 · In terms of Make, a phony target is simply a target that is always out-of-date, so whenever you ask make <phony_target>, it will run, independent from the state of the file system. Some common maketargets that are often phony are: all, install, clean, distclean, TAGS, info, check. See also: GNU make manual: Phony Targets.
How should you use .PHONY in included Makefiles?
WEBDec 11, 2019 · OK, thank you. basically. the .mk modules would never be directly called, but they would be (potentially) included in different "main" Makefiles that would be called. I didn't know if the .PHONY was local to that file or if each time it's encountered in a newly included module the newest statement overrides the previous one. – Kurt E. Clothier.
.PHONY usage in makefile - Stack Overflow
WEBDec 3, 2013 · True. A .PHONY target can have only dependencies, without any rule. In this case, make will not execute any rule, but will check if the dependencies are satisfied (and, if not, will execute their rules). Therefore, in your example, it is correct that both target1 and target2 call dostuff because it is a dependency. answered Dec 3, 2013 at 13:19.
makefile - Declare all targets PHONY - Stack Overflow
WEBJun 12, 2017 · 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. I disagree with the premise that a Makefile with all phony targets should be replaced by arbitrary scripts.
linux - Phony targets in makefile - Stack Overflow
WEBOct 28, 2015 · If "all" is not a phony target, GNU Make checks whether a file named "all" exists and is older than its prerequisites. Try "make -d" and you will see the difference. Another important point is that the recipe of a phony target is always executed. If you take this example: echo "Done". echo "Hello World!"
make implicit rule with force vs .phony - Stack Overflow
WEBMar 16, 2017 · From Phony Targets chapter: Since 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 ...
Is it possible to have multiple .PHONY targets in a GNU makefile?
WEBYes, that's allowed. (If you don't believe me, just try it!) answered Nov 11, 2010 at 22:29. Beta. 98.7k 18 156 155. 29. And in fact you can do that for any target. You can say a: b in one place and a: c in another and then the dependencies for a will be b and c. – tripleee.
Makefile : .PHONY on multiple targets - Stack Overflow
WEBSep 7, 2022 · In a well refined Makefile, it's recommended to mark non-generated targets as .PHONY. Now, the process is pretty simple : suppose there is target1 that must be run any time it's invoked, irrespective of any previous build, then just : .PHONY : target1. target1 :
Why .PHONY:target and not target:.PHONY? - Stack Overflow
WEBJul 20, 2012 · If A depends on B and B is phony, then A is phony too. So the dependency graph .PHONY ← B → A is waay surprising compared to .PHONY → B → A. (Another argument is that an implementation of make must handle the .PHONY target very special.) While this critique may seem rather theoretical (to pointless) - "since make is so ancient, …
Why does .PHONY not work in this situation? - Stack Overflow
WEBJan 25, 2011 · 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 (see Arguments to Specify the Goals).