Horton

Re: meson PGXS compatibility

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org, Nazir Bilal Yavuz <byavuz81@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2022-10-12T05:50:07Z
Lists: 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.

Commits

  1. meson: Add basic PGXS compatibility

  2. autoconf: Move export_dynamic determination to configure

  3. autoconf: Don't AC_SUBST() LD in configure

  4. autoconf: Unify CFLAGS_SSE42 and CFLAGS_ARMV8_CRC32C

  5. autoconf: Rely on ar supporting index creation