Gilbert wrote: > On Sun, 2 Nov 2008 18:51:07 -0800 (PST) > [EMAIL PROTECTED] wrote: > >> I don't have the answer to your quesn, but it would be really nice to be >> able to also log the long form of the compile cmd. This would be useful in 2 >> cases: >> [1] debug the compile process itself >> [2] figure out compile flags, headers & libs, etc that get passed for each >> file >> >> Maybe an option to toggle between short & long form output, but which >> defaults to long form ? >> >> >> ----- Original Message ---- >> From: Carlos R. Mafra <[EMAIL PROTECTED]> >> Sent: Monday, November 3, 2008 6:36:42 AM >> >> I was trying to beautify the compilation of wmaker, so that instead of all >> those long messages >> gcc -DHAVE_CONFIG_H -I. -I../wrlib -I../WINGs -I/usr/local/include >> -DLOCALEDIR=\"/usr/local/lib/locale\" -fno-strict-aliasing -g -O2 -c >> actions.c >> gcc -DHAVE_CONFIG_H -I. -I../wrlib -I../WINGs -I/usr/local/include >> -DLOCALEDIR=\"/usr/local/lib/locale\" -fno-strict-aliasing -g -O2 -c >> appicon.c >> >> now I have something like this, >> Compiling actions.o >> Compiling appicon.o >> . > > You'd need to make those changes in the Makefile.in files, I believe -maybe > in Makefile.am as well. > Gilbert Ashley
Thanks. So a possible solution would be to use --quiet in the configuration script to define a variable QUIET = @echo Compiling $@; and use $(QUIET)$(CC) everywhere instead of $(CC). That looks like an acceptable solution, because if QUIET is empty then everything is as verbose as before. Will try that later. -- To unsubscribe, send mail to [EMAIL PROTECTED]
