|From:||Andres Freund <andres(at)anarazel(dot)de>|
|To:||Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>|
|Cc:||pgsql-hackers(at)postgresql(dot)org, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|Subject:||Re: meson PGXS compatibility|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 2022-12-01 08:43:19 +0100, Peter Eisentraut wrote:
> On 13.10.22 07:23, Andres Freund wrote:
> > > > 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.
> > Yea, I am happy enough with it now that the bulk is out of src/meson.build and
> > strip isn't set to an outright wrong value.
> How are you planning to proceed with this? I thought it was ready, but it
> hasn't moved in a while.
I basically was hoping for a review of the prerequisite patches I posted at
, particularly 0003 (different approach than before, comparatively large).
Here's an updated version of the patches. There was a stupid copy-paste bug in
the prior version of the 0003 / export_dynamic patch.
I'll push 0001, 0002 shortly. I don't think 0002 is the most elegant approach,
but it's not awful. I'd still like some review for 0003, but will try to push
it in a few days if that's not forthcoming.
|Next Message||Tom Lane||2022-12-01 20:49:42||Re: Error-safe user functions|
|Previous Message||Robert Haas||2022-12-01 20:12:09||Re: Error-safe user functions|