Am 12.01.2009 um 18:23 schrieb Stuart Henderson:
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..)
I could maybe add a mode that still uses .SILENT, but instead out outputting coloured text could output the command line executed. Like replace the yellow printf by outputting the command line and remove the green and red output.
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.
Usually, attaching the definitions of buildsys.mk is enough for that. If they aren't honoured, it's a bug in the buildsys and something I have to track down, not the user :). Removing .SILENT is really only to track down bugs in the buildsys itself. Anyway, do you also patch all those ports using other buildsyses that don't output the command line? If so, you got a lot of work ;)
PS: There's no need to always CC me, I'm on the list. And so are you. That's why I always only send to [email protected] :)
-- Jonathan
PGP.sig
Description: Signierter Teil der Nachricht
