pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Craig Ringer <craig.ringer@2ndquadrant.com>
Cc: Yuriy Zhuravlev <stalkerg@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: WIP: About CMake v2
Date: Fri, 27 Jan 2017 22:20:41 -0500
Message-ID: <e206d615-3833-8790-7043-2bf883131b08@2ndquadrant.com> (raw)
In-Reply-To: <20170127231120.lb2hrc34bcc7fkui@alap3.anarazel.de>
References: <CAB7nPqR_Cxv67kOOOQjrKx9cvc5Yn=9wzJyFoLxdc_qj2+TU9w@mail.gmail.com>
	<0d8bf7e7-db42-44d8-aac5-65ff407cb60f@postgrespro.ru>
	<af9694db-858b-c15a-9c5a-bcbccf933ca0@2ndquadrant.com>
	<CANiD2e_tBS869MHRBUTvUq874mxbG3SkE2_PBO2C4TuWxcXEXQ@mail.gmail.com>
	<22f10946-860e-031e-4440-5aaf67c938a4@2ndquadrant.com>
	<CAB7nPqQrskizbD4Lv980ChMvvSrdy_2aw2hqc4QJQN5Umb-uUw@mail.gmail.com>
	<20170124065848.yawgnrpqihvahj5u@alap3.anarazel.de>
	<CAMsr+YET57YUnePwhs_GMKLwCrPAo_=Q4hc-DrbDxRnYA01qxw@mail.gmail.com>
	<13434.1485265067@sss.pgh.pa.us>
	<e7945b31-0e69-9d49-7c72-522bd08fb3c4@2ndquadrant.com>
	<20170127231120.lb2hrc34bcc7fkui@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 1/27/17 6:11 PM, Andres Freund wrote:
> On 2017-01-27 09:09:36 -0500, Peter Eisentraut wrote:
>> My preferred scenario would be to replace the Windows build system by
>> this first, then refine it, then get rid of Autoconf.
>>
>> The ideal timeline would be to have a ready patch to commit early in a
>> development cycle, then get rid of the Windows build system by the end
>> of it.  Naturally, this would need buy-in from Windows developers.
>>
>> I don't foresee replacing the Autoconf build system by this immediately.
> 
> I'm very strongly against this path, it seems way too likely that we'll
> end up with yet another fragile thing that nobody from the *nix side
> will be able to test.

That's a fair concern, but at least with CMake, someone from the *nix
side *can* test it, whereas right now it's completely separate.

What kind of strategy do you have in mind?

-- 
Peter Eisentraut              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



view thread (160+ messages)  latest in thread

Message-ID: <e206d615-3833-8790-7043-2bf883131b08@2ndquadrant.com>
Permalink:  ../e206d615-3833-8790-7043-2bf883131b08@2ndquadrant.com/
Also on:    postgresql.org/message-id/e206d615-3833-8790-7043-2bf883131b08@2ndquadrant.com

 · 

reply
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: peter.eisentraut@2ndquadrant.com, andres@anarazel.de, tgl@sss.pgh.pa.us, craig.ringer@2ndquadrant.com, stalkerg@gmail.com, michael.paquier@gmail.com
  Subject: Re: WIP: About CMake v2
  In-Reply-To: <e206d615-3833-8790-7043-2bf883131b08@2ndquadrant.com>

* 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