Re: WIP: About CMake v2 - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: WIP: About CMake v2
Date
Msg-id CAMsr+YFK+Ve8q+iFxoNysX0ePPvEvFUdMVZge+VRkJKb2eR9Aw@mail.gmail.com
Whole thread Raw
In response to Re: WIP: About CMake v2  (Yury Zhuravlev <u.zhuravlev@postgrespro.ru>)
Responses Re: WIP: About CMake v2  (Michael Paquier <michael.paquier@gmail.com>)
Re: WIP: About CMake v2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
<p dir="ltr"><p dir="ltr">On 9 Nov. 2016 06:37, "Yury Zhuravlev" <<a
href="mailto:u.zhuravlev@postgrespro.ru">u.zhuravlev@postgrespro.ru</a>>wrote:<br /> ><br /> >> When I run
cmakewithout options, it seems to do opportunistic feature<br /> >> checking.  For example, it turns on OpenSSL
orPython support if it can<br /> >> find it, otherwise it turns it off.  We need this to be deterministic.<br />
>>Without options, choose the basic feature set, require all other<br /> >> features to be turned on
explicitly,fail if they can't be found.<br /> >> Whatever the Autoconf-based build does now has been fairly
deliberately<br/> >> tuned, so there should be very little reason to deviate from that.<br /> ><br /> >
Thisapproach I see only in Postgres project and not fully understood.<br /> > Can you explain me more what reasons
ledto this approach?<p dir="ltr">It's predictable. The default has the same result for everyone. I quite like it
myself.<br/> 

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: C based plugins, clocks, locks, and configuration variables
Next
From: Venkata B Nagothi
Date:
Subject: Re: patch proposal