Re: WIP: About CMake v2

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, Christopher Browne <cbbrowne(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: About CMake v2
Date: 2015-08-29 21:36:32
Message-ID: 20150829213631.GI2912@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2015-08-29 17:53:26 -0300, Alvaro Herrera wrote:
> >> Therefore, either we will not find any portability problems, or fixing
> >> upstream those we do find will not be terribly difficult.
>
> > Well, the difference to know is that we can't resolve that relatively
> > quickly ourselves, but that it'd rather require $whoever installing a
> > new version of cmake...
>
> Yup. So one of the things we'd want to establish is what's the minimum
> version of cmake we're going to require, and which (hopefully old)
> platforms will we be leaving out in the cold with that?

Just for the record, in Debian land the versions shipped are thus:

oldoldstable (squeeze): 2.8.2 (has 2.8.9 available in squeeze-backports)
oldstable (wheezy): 2.8.9 (has 2.8.11 available in wheezy-backports)
stable (jessie): 3.0.2

VAX support was added in 2.8.11 (bug fixed in Oct. 2012).

I imagine that esoteric platforms are not going to have cmake at all and
are going to need their own installation anyway. Not sure if that's
going to be more onerous than the requirement to install GNU make.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2015-08-29 21:42:11 Re: to_json(NULL) should to return JSON null instead NULL
Previous Message Tom Lane 2015-08-29 21:14:17 Re: WIP: About CMake v2