From mboxrd@z Thu Jan 1 00:00:00 1970 From: gvb.uboot Date: Thu, 24 Jan 2008 19:23:26 -0500 Subject: [U-Boot-Users] RFC: Concise Build Output In-Reply-To: References: <20080124004145.833A52430C@gemini.denx.de> Message-ID: <47992BFE.5000906@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Grant Likely wrote: > On 1/23/08, Wolfgang Denk wrote: >> Dear Jon, >> >> in message you wrote: >>> In the spirit of the Linux and Git build systems, >>> I have a modified U-Boot build system that supports >>> a much more concise output! One of the primary >>> motivations for this style of output is that it >>> will very readily highlight build issues and problems >>> as your build progresses. The original, complete >>> build output is obtainable by simply supplying "V=1" >>> on the make invocation in exactly the same way as >>> both Linux and Git do today. > >> So my question is: which problem are you trying to solve that is not >> already solved by "make -s" or "MAKEALL"? I don't really see the need >> for a solution between no output and full output. YMMV, of course. >> >> Hope I didn't frustrate you - I still appreciate the effort. > > Hey Jon, Wolfgang; > > I think this is a good change myself. The biggest reason is that it > makes the default output terse instead of verbose. I'd hazard to > wager that most developers don't use 'make -s', MAKEALL, or anything > else to trim the output (I certainly don't). By making the default > output terse, with errors and warning visually distinct from progress > indication, in increases the likelyhood that warnings will actually > get seen and fixed (because more people will notice it). > > I say make this change. > > Cheers, > g. Plus my 2 cents if this is a voting matter. gvb