public inbox for [email protected]
help / color / mirror / Atom feedFrom: Igor Korot <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Adrian Klaver <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: Problem linking with Release library
Date: Tue, 12 May 2026 19:52:13 -0700
Message-ID: <CA+FnnTyRimKOOL46xm=r9YeLXR2FMFZ+z0=mGikMGuazP0AfNQ@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwaK8-iFzWK8_Vqn4BjHDi6J-pNHZTkMTqJX+dp_+PyN4Q@mail.gmail.com>
References: <CA+FnnTwW+=MgpA+w_VUQCb=nPqHihGz51pc6TkYh_QX7ext7Ew@mail.gmail.com>
<[email protected]>
<CA+FnnTzMpDBgVprWDVquGQciazVc+8NFnqM9bmdqRgxhL3UTqA@mail.gmail.com>
<[email protected]>
<CA+FnnTxS-j2RivcD7Xk6A0UJSy-cR=W_0zyUUw19XZ9dp_7iCQ@mail.gmail.com>
<[email protected]>
<CA+FnnTxuAtcbPLGKekF1kS-ifUX8BtW5NRu1-8vAfj_qbLPVyQ@mail.gmail.com>
<[email protected]>
<CA+FnnTx-dVEbpfsSdZAb9Htr=1SdVatbcOKLUMpo2WPj6Mv=KQ@mail.gmail.com>
<[email protected]>
<CA+FnnTza8Or-MaoMW3yPgAqCzQnPwQvwku3AJHfiN21fc9kiXA@mail.gmail.com>
<CAKFQuwaK8-iFzWK8_Vqn4BjHDi6J-pNHZTkMTqJX+dp_+PyN4Q@mail.gmail.com>
Hi, David,
On Tue, May 12, 2026 at 6:04 PM David G. Johnston <
[email protected]> wrote:
> On Tuesday, May 12, 2026, Igor Korot <[email protected]> wrote:
>
>>
>> So then I thought about creating MSVC project for building libpq as a
>> dependency. All I need is to produce a basic default build of both Debug
>> and Release builds of libpq only. No server and no ther software needed.
>> Prefer to build version 17.4.
>>
>
>
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=1301c80b2167feb658a738fa4ceb1c23d0991...
>
> You seem to have put yourself into cutting edge PostgreSQL territory while
> remaining firmly old-school on the OS side of things…not usually a good
> place to find oneself.
>
> My LLM guided understanding is your likely 9.6 tool path was removed in
> favor of meson back in 2023. But meson itself is still working out the
> rough edges for stuff like a defined target for a libpq-only build and
> install.
>
> There is no guarantee or real attempt to keep modern supported versions
> running on software obsoleted before they even came into existence. You
> may or may not be able to finagle make/meson to do what you are attempting
> and the desire to help is limited. You may wish to consult an LLM of your
> choice for assistance. For something like this they can be very helpful
> with little downside.
>
What I don’t understand is:
1. There used to be a split builds - one package to build the server and
another to build the client (libpq). This is no longer the case.
PostgreSQL positions itself as client-server RDBMS, so why in order to
build the client I need the full blown server to download?
2. Any reason I need to install additional software for building (or
configuring the build)? You used to provide the Makefile for MSVC build.
What happened to it?
But to the point -
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.
Thank you.
> David J.
>
>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Problem linking with Release library
In-Reply-To: <CA+FnnTyRimKOOL46xm=r9YeLXR2FMFZ+z0=mGikMGuazP0AfNQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox