Re: Use Postgres as meson wrap subproject

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Niyaz Hazigaleyev <hazigaleevniaz(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Elliot Haisley <elliot(dot)haisley(at)outlook(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tristan Partin <tristan(at)neon(dot)tech>
Subject: Re: Use Postgres as meson wrap subproject
Date: 2026-01-05 01:09:56
Message-ID: bf3f0fa9-546b-490d-b8b5-3c501c29c080@proxel.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/4/26 8:32 PM, Niyaz Hazigaleyev wrote:
> You right Eliot Haisley more complete patch because he replaced all occurrences of @SOURCE_DIR@ but I also added include_directories to dependency, so it will not fail to find headers which are included in libpq headers. So if I merge my patch with Eliot’s it should be fine. I can send complete patch after it’s done.

Did you see that Tristan also just patched his own version which seems
like it could potentially be even more complete?

https://www.postgresql.org/message-id/DFEOAWQP27I8.3LHIXYEFCXD25%40partin.io

> About meson wrap subproject. In my projects I really like to have fallback if there is no system lib available or system lib have not compatible version. Basically I use it as package manager for my C/C++ projects, I just put the link to git into wrap file, provide dependency and that’s it, meson does all the work. Ideally everything in my project should be build from scratch without any prebuilt binaries, so I can cross-compile to any platform that I want and build/packaging of project becomes much easier.

Thanks!

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-01-05 01:18:23 Re: Proposal - Enabling btree_gist by default
Previous Message Alastair Turner 2026-01-05 01:03:51 Proposal - Enabling btree_gist by default