MIME-Version: 1.0
In-Reply-To: 
 <CA+FnnTza8Or-MaoMW3yPgAqCzQnPwQvwku3AJHfiN21fc9kiXA@mail.gmail.com>
References: 
 <CA+FnnTwW+=MgpA+w_VUQCb=nPqHihGz51pc6TkYh_QX7ext7Ew@mail.gmail.com>
 <6b6752b9-1af1-4650-8125-06440fdc7ccd@aklaver.com>
 <CA+FnnTzMpDBgVprWDVquGQciazVc+8NFnqM9bmdqRgxhL3UTqA@mail.gmail.com>
 <7f1fdbad-0343-498d-9f15-69bc713915cc@aklaver.com>
 <CA+FnnTxS-j2RivcD7Xk6A0UJSy-cR=W_0zyUUw19XZ9dp_7iCQ@mail.gmail.com>
 <0e96fd4d-a97e-4461-a92e-ed2d7c27d38c@aklaver.com>
 <CA+FnnTxuAtcbPLGKekF1kS-ifUX8BtW5NRu1-8vAfj_qbLPVyQ@mail.gmail.com>
 <a2876055-5b4f-4579-8238-02bbda9113be@aklaver.com>
 <CA+FnnTx-dVEbpfsSdZAb9Htr=1SdVatbcOKLUMpo2WPj6Mv=KQ@mail.gmail.com>
 <ad5f8deb-91eb-4c3b-8cb9-ec466d7fe88f@aklaver.com>
 <CA+FnnTza8Or-MaoMW3yPgAqCzQnPwQvwku3AJHfiN21fc9kiXA@mail.gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Tue, 12 May 2026 18:04:12 -0700
Message-ID: 
 <CAKFQuwaK8-iFzWK8_Vqn4BjHDi6J-pNHZTkMTqJX+dp_+PyN4Q@mail.gmail.com>
Subject: Re: Problem linking with Release library
To: Igor Korot <ikorot01@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>,
	"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000eba6070651a88eb3"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKFQuwaK8-iFzWK8_Vqn4BjHDi6J-pNHZTkMTqJX%2Bdp_%2BPyN4Q%40mail.gmail.com>
Precedence: bulk

--000000000000eba6070651a88eb3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tuesday, May 12, 2026, Igor Korot <ikorot01@gmail.com> 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=3Dpostgresql.git;a=3Dcommit;h=3D1301c8=
0b2167feb658a738fa4ceb1c23d0991e23

You seem to have put yourself into cutting edge PostgreSQL territory while
remaining firmly old-school on the OS side of things=E2=80=A6not 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.

David J.

--000000000000eba6070651a88eb3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tuesday, May 12, 2026, Igor Korot &lt;<a href=3D"mailto:ikorot01@gmail.c=
om">ikorot01@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v dir=3D"auto"><div><br></div><div dir=3D"auto">So then I thought about cre=
ating MSVC project for building libpq as a dependency. All I need is to pro=
duce 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.</div><=
/div></blockquote><div><br></div><div>=C2=A0<a href=3D"https://git.postgres=
ql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommit;h=3D1301c80b2167feb658a738fa4c=
eb1c23d0991e23">https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dc=
ommit;h=3D1301c80b2167feb658a738fa4ceb1c23d0991e23</a></div><div><br></div>=
<div>You seem to have put yourself into cutting edge PostgreSQL territory w=
hile remaining firmly old-school on the OS side of things=E2=80=A6not usual=
ly a good place to find oneself.</div><div><br></div><div>My LLM guided und=
erstanding is your likely 9.6 tool path was removed in favor of meson back =
in 2023.=C2=A0 But meson itself is still working out the rough edges for st=
uff like a defined target for a libpq-only build and install.</div><div><br=
></div><div>There is no guarantee or real attempt to keep modern supported =
versions running on software obsoleted before they even came into existence=
.=C2=A0 You may or may not be able to finagle make/meson to do what you are=
 attempting and the desire to help is limited.=C2=A0 You may wish to consul=
t an LLM of your choice for assistance.=C2=A0 For something like this they =
can be very helpful with little downside.</div><div><br></div><div>David J.=
</div><div><br></div>

--000000000000eba6070651a88eb3--