[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: Bob Friesenhahn
Subject: Re: [PATCH] build: use automake's --silent-rules option when possible
Date: Sun, 29 Mar 2009 11:40:15 -0500 (CDT)

On Sun, 29 Mar 2009, Jan Engelhardt wrote:

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
                @echo CFLAGS used: ${AM_CFLAGS} ${CFLAGS}

Unfortunately, this is not sufficient to show everything. Not all files are built with the same options. A project may have many different built products which use different includes, libraries, and defines.

This is why I think that the 'silent' mode is most useful to package maintainers using carefully tailored/tested build environments and least useful for end-users.

As a package maintainer it is MY responsibility to wring out any build warnings so that end-users never see them. When trying to get rid of any remaining warnings, the silent mode is very useful. If I am building software written my someone else on my system, I prefer to see everything so that when the build malfunctions after an hour or two, the evidence is plain to see.

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]