Am 04.05.2019 um 19:29 schrieb Roland Illig:
Am 04.05.2019 um 17:59 schrieb Jason Bacon:
There's been an intermittent issue running multiple targets with bmake
for as long as I can remember:
Sometimes only the first target runs and sometimes all targets work.
It's not really sometimes. It's only surprising when any of the "clean"
targets is involved.
To fix at least the 99% of the most common workflows involving one of
the "clean" targets, the appended patch looks whether one of the "clean"
targets is given in the command line, and if it is, it treats all cookie
files as nonexistent, assuming the "clean" targets will remove them
early enough.
This makes "bmake clean depends" equivalent to "bmake clean && bmake
depends".
It doesn't work for "bmake wrapper clean build", but that command hasn't
worked before either and is most probably not in anyone's workflow. If I
were wrong, I'd like to know.
I can only think of these legitimate workflows, which are all covered:
1. first clean, then do something productive
2. first clean, then do something productive, then clean again
3. do something productive, then clean