Re: Debugging postgres on Windows - could not open directory "/lib" - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Debugging postgres on Windows - could not open directory "/lib"
Date
Msg-id 50231f4e-fe00-4ba2-b56c-250f3dbc4d63@aklaver.com
Whole thread Raw
In response to Re: Debugging postgres on Windows - could not open directory "/lib"  (Cathy Xie <cathy.xyy@gmail.com>)
Responses Re: Debugging postgres on Windows - could not open directory "/lib"
List pgsql-general
On 2/21/23 17:18, Cathy Xie wrote:
> 
> 
> On Wed, Feb 22, 2023 at 6:54 AM Adrian Klaver <adrian.klaver@aklaver.com 

> 
> Hi Adrian,
> 
> Thanks for your email!
> 
>     1) How did you build it?
> 
> 
> I installed ActivateState Perl, Bison, and Flex. Then I ran the command 
> ```build Debug``` under directory postgres/src/tools/msvc
> 
>     2) Open pgsql.sln in a text editor and report the results here.
> 
> Here was the result when I opened pgsql.sln in Visual Studio 2022, and 
> ran the postgres.exe.

1) That just repeats the error message from your previous post.

2) Please use copy and paste of text instead of screenshots. Those of us 
with old eyes would appreciate it.

3) Per previous request:

    Open pgsql.sln in a text editor and report the results here.

    It is the contents of pgsql.sln that I am looking for.

> 
> Screenshot_20230222_091621.png
> I look forward to hearing back from you.
> 
> Thanks!
> Cathy
> 
> 
>      >
>      > Best regards,
>      > Cathy
>      >
> 
>     -- 
>     Adrian Klaver
>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Jeffrey Walton
Date:
Subject: Re: Memory leak using when using libpq PQExecParams() CRYPTO_zalloc()
Next
From: Neethu P
Date:
Subject: Re: Event Triggers unable to capture the DDL script executed