$ cat Makefile
%.all.kmz: $(addsuffix .kml, $(addsuffix .$*.lines,0 1) $(addsuffix
.$*.labels,0 1))
ls $*
$ make nnn.all.kmz
Here, upon reaching the colon, the make program already has all the
information it needs to set $* to "nnn".
Alas, it waits until the "ls" line to get around to finally setting it.
It shouldn't dawdle, but instead set $*, and in fact also $@ too, right
away, upon reaching the colon. Why? Because as you see we can make great
use of them to the right of the colon.
Or, document that those variables are purposely not expanded after the
colon, and add examples of what terrible thing might happen if they
were.
Or, document that they are purposely not expanded, to maintain
compatibility. But in fact there is no compatibility to maintain, as in
the past nobody would have used $* or $@ after the colon, because they
were useless.
Anyway, just like (info "(make) Computed Names") says, "This restriction
could be removed in the future if that change is shown to be a good
idea." Same applies to $* and $@.
Yes, even for just
bla.%: $@.zzz $*.eee; qq
$ make bla.rrr
should already know it should now make bla.rrr.zzz and bla.eee. Not make
just ".zzz" and ".eee".
GNU Make 4.3
