| From: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com> |
|---|---|
| To: | YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: About CMake v2 |
| Date: | 2016-11-08 22:54:03 |
| Message-ID: | CAMsr+YFK+Ve8q+iFxoNysX0ePPvEvFUdMVZge+VRkJKb2eR9Aw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9 Nov. 2016 06:37, "Yury Zhuravlev" <u(dot)zhuravlev(at)postgrespro(dot)ru> wrote:
>
>> When I run cmake without options, it seems to do opportunistic feature
>> checking. For example, it turns on OpenSSL or Python support if it can
>> find it, otherwise it turns it off. We need this to be deterministic.
>> Without options, choose the basic feature set, require all other
>> features to be turned on explicitly, fail if they can't be found.
>> Whatever the Autoconf-based build does now has been fairly deliberately
>> tuned, so there should be very little reason to deviate from that.
>
> This approach I see only in Postgres project and not fully understood.
> Can you explain me more what reasons led to this approach?
It's predictable. The default has the same result for everyone. I quite
like it myself.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-11-08 22:58:26 | Re: C based plugins, clocks, locks, and configuration variables |
| Previous Message | Venkata B Nagothi | 2016-11-08 22:47:36 | Re: patch proposal |