Hi, Adrian,
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-STUDIO
>
> 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.