From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Browne <cbbrowne@gmail.com>
cc: YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>,
 PostgreSQL Mailing Lists <pgsql-hackers@postgresql.org>
Subject: Re: WIP: About CMake v2
In-reply-to: 
 <CAFNqd5V-LWwWCfa_o1nxJB=jDMQTrAp51Z9c-dhBLsLjCFvb+A@mail.gmail.com>
References: <4184974.kkvGJ5GoEX@dinodell>
 <CAFNqd5V-LWwWCfa_o1nxJB=jDMQTrAp51Z9c-dhBLsLjCFvb+A@mail.gmail.com>
Comments: In-reply-to Christopher Browne <cbbrowne@gmail.com>
 message dated "Fri, 28 Aug 2015 13:51:30 -0400"
Date: Fri, 28 Aug 2015 14:04:11 -0400
Message-ID: <26858.1440785051@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Christopher Browne <cbbrowne@gmail.com> writes:
> (Does CMake run on a VAX 11/780??  :-))

Yeah.  I see the two major risks as being:

1. We limit ourselves to platforms that cmake works on.

2. We lose the ability to handle weird special-case tests that are
possible (if not necessarily pleasant) with autoconf/gmake.

I might be overly worried about #2 --- but the impression I have of cmake
is that they've spent lots of time on "make easy cases easy" and maybe not
enough on "make hard cases possible".

Anyway, we won't know unless somebody tries it.  There will certainly be
some pluses and some minuses, and we'll have to decide whether the pluses
outweigh the minuses.  I don't think we can tell that without a fairly
detailed attempt at making it work.

			regards, tom lane


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers