Can be done with functions, e.g., the second prereq is $(word 2,$+). Given that it’s straightforward composition of documented features, you’d want to document it only if it were very commonly needed. Which it isn’t. That’s my two cents, anyway.
Sam On Fri, Jun 14, 2019 at 11:29 PM Dan Jacobson <[email protected]> wrote: > (info "(make) Automatic Variables") has > > '$<' The name of the first prerequisite... > '$?' The names of all the prerequisites that are newer than the target... > '$^' The names of all the prerequisites, with spaces between them... > '$+' This is like '$^', but prerequisites listed more than once are... > '$|' The names of all the order-only prerequisites... > > OK, OK, OK, OK, OK! > > But it really should also mention the official recommended way to (drum > roll)... > > Get the name of the second prerequisite. > > OK, the first born son inherits the throne. But at least document the > workaround for accessing the second born son. Thanks. P.S., third born > too. And how about last born also. > > I'm not asking for code changes, just officially documenting the proper > way to access them. > > _______________________________________________ > Bug-make mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-make >
_______________________________________________ Bug-make mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-make
