Re: meson PGXS compatibility - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: meson PGXS compatibility
Date
Msg-id 13f9fea7-e196-3956-f297-98797144c20c@enterprisedb.com
Whole thread Raw
In response to meson PGXS compatibility  (Andres Freund <andres@anarazel.de>)
Responses Re: meson PGXS compatibility  (John Naylor <john.naylor@enterprisedb.com>)
Re: meson PGXS compatibility  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 05.10.22 22:07, Andres Freund wrote:
> 0001: autoconf: Unify CFLAGS_SSE42 and CFLAGS_ARMV8_CRC32C

I wonder, there has been some work lately to use SIMD and such in other 
places.  Would that affect what kinds of extra CPU-specific compiler 
flags and combinations we might need?

Seems fine otherwise.
> 0005: meson: Add PGXS compatibility
> 
>    The actual meson PGXS compatibility. Plenty more replacements to do, but
>    suffices to build common extensions on a few platforms.
> 
>    What level of completeness do we want to require here?

I have tried this with a few extensions.  Seems to work alright.  I 
don't think we need to overthink this.  The way it's set up, if someone 
needs additional variables set, they can easily be added.




pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: TRAP: FailedAssertion("prev_first_lsn < cur_txn->first_lsn", File: "reorderbuffer.c", Line: 927, PID: 568639)
Next
From: Michael Paquier
Date:
Subject: Re: pg_upgrade failing for 200+ million Large Objects