Follow-up Comment #4, bug #40225 (project make):
Trying to make the output order deterministic seems to be the wrong approach
to me. It'd be better to separate the build log out into lots of little files
corresponding to each output file. I reckon this isn't too hard with a guile
script. From guile, you set up a pipe and fork. Then you add a $(info $@ ...)
to the start of the commands for every build rule. The forked guile would read
these from the pipe and filter them.
As a test, I wrote a guile script (which I've attached to the bug) which does
the pipe/fork however it execs tee to save a copy of the build output in a
file. I'm new to Guile so sorry if it is somewhat crude but I think it does
prove the concept.
Does anyone know how I can avoid the guile messages about auto-compiling the
script given that I can't impose environment variables on users of the
Makefile? I've tried adding a path to the compiled file to %load-compiled-path
before calling (load "...") in the Makefile.. I've also tried a putenv.
(file #29386)
_______________________________________________________
Additional Item Attachment:
File name: buildlog.scm Size:0 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?40225>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
