Re: Problem linking with Release library
Peter J. Holzer <hjp-pgsql@hjp.at>
From: "Peter J. Holzer" <hjp-pgsql@hjp.at>
To: pgsql-general@lists.postgresql.org
Date: 2026-05-14T08:38:55Z
Lists: pgsql-general
On 2026-05-12 21:59:41 -0700, Igor Korot wrote:
> On Tue, May 12, 2026 at 8:10 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
>
> On Tue, May 12, 2026 at 10:52 PM Igor Korot <ikorot01@gmail.com> wrote:
> [snip]
>
> I’m not running Postgres server. It is running on the different
> machines. All I need is to build the client library. Why can’t I? Why
> it should matter what software (OS/compiler) I’m using? As long as I
> can successfully build my software and test it it should be fine.
>
>
> David made it pretty clear: the PGDG changed the toolchain,
>
>
> It didn’t change the toolchain - it changed configuration tools. But it’s not
> the point.
They switched from Make to Meson. In my book the build automation tool
is very much part of the toolchain.
> The point I’m making is that the software was providing the makefile and now it
> does not.
Because they now use Meson instead of Make. Meson doesn't use Makefiles
but dependency files with a different syntax.
hjp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | hjp@hjp.at | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Remove MSVC scripts
- 1301c80b2167 17.0 cited