I'm looking for insight in the area of how make handles background
processes started from recipes.
Let me
start
with
a
summary
of
my
real-word scenario: we have a Linux makefile which is large, complex and
proprietary but in the end all it does is compile a bunch of objects and
link them t
NE
Note that make says "MAKE DONE" and exits back to the shell, then 5 seconds
later the "PYTHON JOB DONE" arrives which is exactly the behavior desired.
But in the real makefile the "PYTHON JOB DONE" shows up before "MAKE DONE"
meaning that make has wa
Is there any direct support for showing, or have people come up with clever
ways of finding, unnecessary lines in the DAG? Trivial example: in a
typical HelloWorld build model the "hello" executable depends on hello.o
which in turn depends on hello.c. If there was an explicit direct
dependency of h
