From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: YUriy Zhuravlev <u.zhuravlev@postgrespro.ru>
Cc: Christopher Browne <cbbrowne@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: WIP: About CMake v2
Date: Sat, 29 Aug 2015 17:53:26 -0300
Message-ID: <20150829205326.GH2912@alvherre.pgsql> (raw)
In-Reply-To: <2844430.7oqKMGMpEj@dinodell>
References: <4184974.kkvGJ5GoEX@dinodell>
<CAFNqd5V-LWwWCfa_o1nxJB=jDMQTrAp51Z9c-dhBLsLjCFvb+A@mail.gmail.com>
<2844430.7oqKMGMpEj@dinodell>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
YUriy Zhuravlev wrote:
> On Friday 28 August 2015 13:51:30 you wrote:
> > It's broadly interesting, but since it bakes in a build dependency on
> > CMake, there is some risk that the dependencies become an insurmountable
> > problem.
> >
> > (Does CMake run on a VAX 11/780?? :-))
>
> http://public.kitware.com/Bug/view.php?id=13605 you about this?
Hmm, what this closed bug report says to me is that 1) cmake developers
take portability seriously, 2) all common and even some not-so-common
platforms are likely to be in hand already. Therefore, either we will
not find any portability problems, or fixing upstream those we do find
will not be terribly difficult.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, u.zhuravlev@postgrespro.ru, cbbrowne@gmail.com
Subject: Re: WIP: About CMake v2
In-Reply-To: <20150829205326.GH2912@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox