[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] build: use automake's --silent-rules option when possible
From: |
Jan Engelhardt |
Subject: |
Re: [PATCH] build: use automake's --silent-rules option when possible |
Date: |
Sun, 29 Mar 2009 18:26:52 +0200 (CEST) |
User-agent: |
Alpine 2.00 (LSU 1167 2008-08-23) |
On Sunday 2009-03-29 17:43, Bob Friesenhahn wrote:
>
> We can suggest using "make V=1" but end users are most likely to execute
> './configure', 'make', 'make install' without reading most of the package
> install documentation.
>[...]
> By sufficiently noisy I mean that the user should be able to see the
> preprocessor and library search paths and any defines provided via the command
> line so they can be sure that the right bits are being used.
Some projects' code outputs the flags at the end of configure,
I think that's a nice overview, but actually, that's outside automake ;-)
As for automake, this lil hack could do something similar
# -*- Makefile -*-
BUILT_SOURCES = show-flags
show-flags:
@echo CFLAGS used: ${AM_CFLAGS} ${CFLAGS}
- Re: [PATCH] build: use automake's --silent-rules option when possible, (continued)
Re: [PATCH] build: use automake's --silent-rules option when possible, Ralf Corsepius, 2009/03/28
Re: [PATCH] build: use automake's --silent-rules option when possible, Bob Friesenhahn, 2009/03/29
Re: [PATCH] build: use automake's --silent-rules option when possible, Thomas Dickey, 2009/03/29
Re: [PATCH] build: use automake's --silent-rules option when possible, Bob Friesenhahn, 2009/03/29
Re: [PATCH] build: use automake's --silent-rules option when possible, Thomas Dickey, 2009/03/29