[PATCH] makefiles: Optionally emit automake-style "silent" output.

Jeff Smith whydoubt at gmail.com
Wed Sep 30 11:16:27 CDT 2020


On Wed, Sep 30, 2020 at 10:50 AM Zebediah Figura <z.figura12 at gmail.com> wrote:
> On 9/30/20 3:08 AM, Rémi Bernon wrote:
> > On 9/30/20 9:12 AM, Jeff Smith wrote:
> >> FWIW, when I attempted a similar patch last September,
> >> I got pushback from Alexandre due to him not considering
> >> nested macro expansion as portable.
> >> I also got pushback against enabling by default.
> >>
> >> It seems that the conservative approach would be to
> >> 1. make the default for silent rules disabled, and
> >> 2. only output the WINE_V_ rules to the Makefile
> >>     if silent rules are enabled.
> >>
> >> On Mon, Sep 14, 2020 at 10:42 PM Zebediah Figura <z.figura12 at gmail.com> wrote:
> >>>
> >>> The subject line of this patch may be a little misleading, upon
> >>> reflection, since it's enabled by default. That fact could easily be
> >>> changed; I only did so since automake also enables its silent output by
> >>> default.
> >>>
> >>
> >
> > Note that you can also enable fully silent build by defining a .SILENT:
> > rule, in a wrapper Makefile for instance. I'm personally not really sure
> > how useful a semi-silent build is.
> >
>
> Unfortunate. I would have appreciated a patch like this, as it helps me
> gauge build progress, but if there's no way to do it portably then I'll
> just drop it.

In addition, with partial builds, this makes it easier to see at a
glance what actually built.
While some don't care for them, there is definitely value in quieter builds.

When I tried last year, I just decided to let it lie.
Coming back to it though, I really would like to see some form of this
get accepted.
I do have ideas on how to mold it into something acceptable, though
there are a couple
of details I haven't worked out.



More information about the wine-devel mailing list