On 2009/01/12 16:20, Jonathan Schleifer wrote: > Am 12.01.2009 um 16:14 schrieb Federico G. Schwindt: > >> I don't know others, but as developer I would never prefer colorful >> output over the real one, and I don't find it very useful, neither >> for me >> nor for anyone who might need to report issues during building. > > Well, you see the compiler and linker flags if you look at the > Makefile. This is usually enough. If those aren't adeded on build for > some reason, that's a bug in the buildsys - and then you'd need to > disable .SILENT: :) Normal users should never need to do that, and > even developers, if they aren't buildsys developers, usually never > need to do that. > >> I think as it is with the diff is fine, it's simple and does the job. > > I consider that very ugly. You have useless printfs there and also the > the printfs in the output. So you actually see a loop and the text > twice.
imho it is a bit ugly, but if being able to see the compiler command lines requires slightly ugly output, I'd rather have the ugly output. (i'd prefer it even more with a proper option that hides the internal build system logic and the lines like "CC foo.c" and just prints the command invocations..) if people are tracking down a build problem, or if they're grepping logs from a bulk build looking for something, or even the simple case of making sure CC/CFLAGS are honoured, full command lines are often invaluable.
