Re: Windows default locale vs initdb - Mailing list pgsql-hackers

From Ertan Küçükoglu
Subject Re: Windows default locale vs initdb
Date
Msg-id CAH2i4ydZq-ovi4oanmsd4=sq3rXwoZ3pyMc_034s94MPVgdsaQ@mail.gmail.com
Whole thread Raw
In response to Re: Windows default locale vs initdb  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Windows default locale vs initdb
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.com>, 22 Tem 2024 Pzt, 14:00 tarihinde şunu yazdı:
Sorry, I didn't mean to put you on the spot :-)  Yeah you'd need to
install a compiler, various libraries and tools to be able to build
form source with a patch.  Unfortunately I'm not the best person to
explain how to do that on Windows as I don't use it.  Honestly it
might be a bit too much new stuff to figure out at once just to test
this small patch.  What I'd be hoping for is confirmation that there
are no weird unintended consequences or problems I'm not seeing since
I'm writing blind patches based on documentation only, but it's
probably too much to ask to figure out the whole development
environment and then go on an open ended expedition looking for
unknown problems.

I already installed Visual Studio 2022 with C++ support as suggested in https://www.postgresql.org/docs/current/install-windows-full.html
I cloned codes in the system.
But, I cannot find any "src/tools/msvc" directory. It is missing.
Document states I need everything in there
"The tools for building using Visual C++ or Platform SDK are in the src\tools\msvc directory."
It seems I will need help setting up the build environment.

pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: CI, macports, darwin version problems
Next
From: Andrew Dunstan
Date:
Subject: Re: xid_wraparound tests intermittent failure.