Re: Problem linking with Release library

Hi, Adrian,

On Fri, May 8, 2026 at 10:46 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
>
>
> On 5/8/26 11:12 AM, Igor Korot wrote:
> > Hi, Adrian,
> >
> > On Fri, May 8, 2026 at 11:24 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> >>
> >> On 5/8/26 8:34 AM, Igor Korot wrote:
> >>> Hi, Adrian,
> >>>
> >>> On Fri, May 8, 2026 at 7:32 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> >>> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
> >>>
> >>> On 5/7/26 11:36 PM, Igor Korot wrote:
> >>> > Hi,
> >>> > A long time ago I built both Debug and Release versions of libpq.
> >>>
> >>> Define what distinguishes Debug from Release version.
> >>>
> >>>
> >>> Debug - on *nix-like systems it compiles with “-g”. On windows it has
> >>> references to the source code.
> >>>
> >>> Release - it’s stripped from the source code references.
> >>
> >> What are the specific parameters you use to compile in each case?
> >
> > I don't remember already.
> > But I THINK I did use default all the way through.
>
> To me it looks like you need to review your tool chain and build process.

So I'd like to get back to this.

Turns out I had a very old 9.6 version.

Now I checked and on my Linux box I have 17.4

What I'd like to do is integrate libpq building inside MSVC as a dependency.

Is it possible?

If not - what's the simplest possible way of building the library?

Thank you

>
>
> >> --
> >> Adrian Klaver
> >> adrian(dot)klaver(at)aklaver(dot)com
>