On 9 Nov. 2016 06:37, "Yury Zhuravlev" <u.zhurav...@postgrespro.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.

Reply via email to