public inbox for pgsql-general@postgresql.org
help / color / mirror / Atom feedFrom: Igor Korot <ikorot01@gmail.com>
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Problem linking with Release library
Date: Tue, 12 May 2026 17:21:09 -0700
Message-ID: <CA+FnnTza8Or-MaoMW3yPgAqCzQnPwQvwku3AJHfiN21fc9kiXA@mail.gmail.com> (raw)
In-Reply-To: <ad5f8deb-91eb-4c3b-8cb9-ec466d7fe88f@aklaver.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>
Hi, Adrian,
On Tue, May 12, 2026, 5:03 PM Adrian Klaver <adrian.klaver@aklaver.com>
wrote:
> On 5/12/26 2:12 PM, Igor Korot wrote:
> > Adrian,
> >
>
> >> Have you looked at?:
> >>
> >>
> https://www.postgresql.org/docs/current/installation-platform-notes.html#INSTALLATION-NOTES-VISUAL-S...
> >
> > Also - I'm not interested in downloading the whole server. I already
> > have it installed on the other machine.
> >
> > I want libpq Debug and Release versions only as most developers do.
>
> Honestly, at this point I have no idea what your goal is. You will need
> to provide a detailed explanation of what you did before that worked and
> the conditions that where in place that made it work. Then provide
> detailed information on your current conditions and what you want the
> result to be.
>
What is want is to have a Debug and Release of libpq on this box.
That's it.
No server and no server utilities.
Just libpq. As shared dynamic library.
In the past what I did was to grab the 9.6 version and build the libpq with
simply run nmake.
I never needed to use Release version as I was working with Debug one.
However couple of days ago I needed to build Release version of my software
and so that's what I tried.
Unfortunately building Release version resulted in the linking error I was
mentioned in the OP.
Debug version was working fine.
Then I realized that there is a mismatch with the versions on my Windows
and Linux machines and as I tried to stay with the same version around
different OSes, I tried to get 17.4.
But unfortunately I was not able to build it easily with just nmake as in
the past because now it requires to install many other unrelated software.
I have no idea why the Release build failed on 9.6. But Debug one worked
for years
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.
I have MSVC 2017 on Windows 8.1. This setup was working fine with libpq
Debug version 9.6
I hope now it's clear
Let me know if it's not.
Thank you.
> >
> > Thank you.
> >
> >>
> >>>
> >>> Thank you
> >>>
> >>>>
> >>>>
> >>>>>> --
> >>>>>> Adrian Klaver
> >>>>>> adrian.klaver@aklaver.com
> >>>>
> >>
> >>
> >> --
> >> Adrian Klaver
> >> adrian.klaver@aklaver.com
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
>
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: pgsql-general@postgresql.org
Cc: ikorot01@gmail.com, adrian.klaver@aklaver.com, pgsql-general@lists.postgresql.org
Subject: Re: Problem linking with Release library
In-Reply-To: <CA+FnnTza8Or-MaoMW3yPgAqCzQnPwQvwku3AJHfiN21fc9kiXA@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