[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GOP-PROP 5: build system output (update)
From: |
Graham Percival |
Subject: |
Re: GOP-PROP 5: build system output (update) |
Date: |
Sat, 16 Jul 2011 10:36:11 -0700 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Fri, Jul 15, 2011 at 05:20:02PM +0100, Phil Holmes wrote:
> ----- Original Message ----- From: "Graham Percival"
> <address@hidden>
> >On Fri, Jul 15, 2011 at 02:20:51PM +0100, Phil Holmes wrote:
> >I'm not certain if it's possible to cause make(1) to automatically
> >put its output into a logfile in addition to the console.
>
> From my reading of the manual, there is no option to redirect
> make output to a logfile. I always do this with a command line
> redirect. AFAICS the only other way to do this would be to wrap
> make in another program that captures its output to log and
> console - Kili wrote something like this. However, I'm
> personally rather loathe to do such wrapping.
Good point. Ok, I've modified the proposal accordingly.
> >>I think there should be an option to turn it all back on if you want
> >>- a sort of inverse of QUIET_BUILD. We should also get rid of the
> >>QUIET_BUILD variable completely.
> >
> >Agreed. Maybe using the V=1 thing that Jan was talking about?
>
> That sort of thing. I'd propose a variable called VERBOSE that
> would have to be set to get the output on screen.
I think we should use whatever variable is normally used for this
task. That may well be VERBOSE, but if it's something else, I
think we should use that something else. Or maybe it's normally
done with either VERBOSE or V ?
Cheers,
- Graham