Hi.
Is it possible to reduce the amount of information printed by
the Makefiles when compiling or linking?
Simply using the .SILENT: ... pseudo-target goes a little too
far, I would prefer something similar to the behaviour of the
Linux kernel Makefiles, e.g., printing only the line
Hi,
Simply using the .SILENT: ... pseudo-target goes a little too
far, I would prefer something similar to the behaviour of the
Linux kernel Makefiles, e.g., printing only the line
Compiling foo.c
when foo.c is compiled.
Is there a portable way of doing this?
Modifying the rules that
On Thu, 17 Jun 2004, Simon Richter wrote:
Hi,
Simply using the .SILENT: ... pseudo-target goes a little too
far, I would prefer something similar to the behaviour of the
Linux kernel Makefiles, e.g., printing only the line
Compiling foo.c
when foo.c is compiled.
Is there a
Hi,
Simply using the .SILENT: ... pseudo-target goes a little too
far, I would prefer something similar to the behaviour of the
Linux kernel Makefiles, e.g., printing only the line
Compiling foo.c
when foo.c is compiled.
Is there a portable way of doing this?
Modifying the
On Fri, 18 Jun 2004 01:02:54 +0200, Steffen Boerm [EMAIL PROTECTED] said:
Of course I would like to have an _option_ to view the full command
line when porting my library to a new operating environment, but
when I'm working on the C sources, it is much easier to find
compiler warnings if
On Thu, 17 Jun 2004, Paul F. Kunz wrote:
Try compiling under emacs. Do ESC-x, then type compile in a
buffer that has a file in the same directory as your Makefile. After
compilation, you can find the warnings and errors with Ctrl-x `.
This not only shows you the warning, but opens the
