On 10/4/2012 12:11 PM, Gregory Szorc wrote:
#1 is a larger problem with no easy solution. Without significantly
altering how make/pymake work, about the best we can do is parse the
process output of the build and try to print something intelligent if
the build failed. Unfortunately, this is far from robust because
parallel make sometimes interleaves output from multiple processes on
stdout.
There are a couple ways to approach the problem. The pymake-specific way
is to redirect output from commands to a temporary file/pipe and feed
that back to the driver in a more intelligent way. This is not trivial
but probably not super-hard. You'd end up with a lot of possibilities
there too, such as "make silently *except* when an error occurs, in
which case dump the full log".
The other way to do this is to build the log redirection into the
individual commands (compilation) which are most common. This would work
for standard `make`.
Probably you really want a combination of those, since pymake already
does compilation using a native command (IIRC) so you can do the pymake
redirection in that command and the gmake redirection using some shell
scripting structure.
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
