From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Shrink volume of default make output |
Date: | 2017-01-04 03:03:37 |
Message-ID: | CAMsr+YFywLS0B2psD6rkV2A_J3qjVL28ibdPzmD7WW+kVUU2Kw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3 January 2017 at 05:37, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> The recent thread about compiler warnings got me thinking about how it's
> essentially impossible to notice warnings with default make output. Perhaps
> everyone just uses make -s by default, though that's a bit annoying since
> you get no output unless something does warn (and then you don't know what
> directory it was in).
For that latter reason I'd love to be rid of recursive make. But it's
not that bad since we don't have many files of the same names; I just
find myself using vim's ctrlp a lot.
Personally I'd rather let it lie, use 'make -s' and wait for cmake.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2017-01-04 03:15:16 | Re: Logical decoding - filtering tables |
Previous Message | Tomas Vondra | 2017-01-04 02:35:15 | Re: multivariate statistics (v19) |