looking at someone else's Makefile, did a full build and saved all
the output for subsequent perusal thusly:
$ make ... > /tmp/stuff 2>&1
weirdly(?), there is a target which first runs a number of simple
linux commands (rm, mkdir, ...), then invokes "foreach" a couple
times to call some fu
On Sat, 2019-10-12 at 08:13 -0400, Robert P. J. Day wrote:
> weirdly(?), there is a target which first runs a number of simple
> linux commands (rm, mkdir, ...), then invokes "foreach" a couple
> times to call some functions.
>
> i say "weirdly" because the output shows the "foreach" invocatio
On Sat, 12 Oct 2019, Paul Smith wrote:
> On Sat, 2019-10-12 at 08:13 -0400, Robert P. J. Day wrote:
> > weirdly(?), there is a target which first runs a number of simple
> > linux commands (rm, mkdir, ...), then invokes "foreach" a couple
> > times to call some functions.
> >
> > i say "weirdl
i'm currently working my way through the (version 4.2) make manual
and, occasionally, run across things that could be worded better.
eg: section 4.2, "Types of Prerequisites", contains an example to
demonstrate order-only prerequisites, but the example makes use of the
OUTPUT_OPTION variable
On Sat, 2019-10-12 at 12:27 -0400, Robert P. J. Day wrote:
> eg: section 4.2, "Types of Prerequisites", contains an example to
> demonstrate order-only prerequisites, but the example makes use of the
> OUTPUT_OPTION variable which has not yet been explained, which might
> confuse some readers.
>
