Re: WIP: About CMake v2
От | Craig Ringer |
---|---|
Тема | Re: WIP: About CMake v2 |
Дата | |
Msg-id | CAMsr+YFK+Ve8q+iFxoNysX0ePPvEvFUdMVZge+VRkJKb2eR9Aw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WIP: About CMake v2 (Yury Zhuravlev <u.zhuravlev@postgrespro.ru>) |
Ответы |
Re: WIP: About CMake v2
Re: WIP: About CMake v2 |
Список | 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 по дате отправления: