Re: Is a modern build system acceptable for older platforms

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Hartmut Holzgraefe <hartmut(dot)holzgraefe(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Yuriy Zhuravlev <stalkerg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Is a modern build system acceptable for older platforms
Date: 2018-05-02 22:14:50
Message-ID: 9224.1525299290@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Now you could argue that we could just rewrite to non-recursive
> make. But that'd be nearly as much work as migrating to another
> buildsystem.

I'm sure it'd be a significant amount of work ... but it wouldn't require
redesigning any configuration or portability hacks, nor any change in
tool prerequisites, and at least in principle it wouldn't require changes
in users' build scripts. So I think claiming it's as expensive as
migrating to cmake is almost certainly wrong.

(I don't know offhand if tricks like "build plpython only" would
still work unchanged, but that's a sufficiently niche usage that
I'd not be too concerned about making those people adapt their
scripts.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Catalin Iacob 2018-05-02 22:32:39 Re: Is a modern build system acceptable for older platforms
Previous Message Tom Lane 2018-05-02 22:08:09 Re: Optimize Arm64 crc32c implementation in Postgresql