cleaned!

git ls-files --eol *.vcxproj*
shows that the repository has mixed line endings in VS build system files
maybe it makes sense to add .gitattributes and run at least
git add --renormalize *.vcxproj*

cleaned!

git ls-files --eol .vcxproj shows that the repository has mixed line endings in VS build system files maybe it makes sense to add .gitattributes and run at least git add --renormalize .vcxproj

Thanks.
Yes, tidying up the line endings can be done in a separate PR (similar to #4154), and then put the revision in .git-blame-ignore-revs so it won't show up in git blame.

Looks okay to me, but since I rarely touch Windows, I'll leave the approval to @nanangizz and @trengginas .

Tested with VS 2022 only, looks okay.
The docs says we support older VS versions (2015-2019), perhaps @trengginas can check.

Tested on VS2015 and VS2019

Tested on VS2015 and VS2019

Both can build the lib? Any additional steps, e.g: changing the build tools set version to older/140, required? As I read somewhere that VS2015 cannot use build tool set 143 (which is set in the property sheet).

For VS2019 and VS2015, change the BuildToolset on pjproject-vs14-common-config.props

https://github.com/LeonidGoltsblat/pjproject/blob/31f8676c37847060da6ace988a160f2905b3f723/build/vs/pjproject-vs14-common-config.props#L26

To v140
Notes: for VS2019 it supports buildtoolset up to v142.

For VS2019 and VS2015, change the BuildToolset on pjproject-vs14-common-config.props

https://github.com/LeonidGoltsblat/pjproject/blob/31f8676c37847060da6ace988a160f2905b3f723/build/vs/pjproject-vs14-common-config.props#L26

To v140 Notes: for VS2019 it supports buildtoolset up to v142.

Okay, perhaps it is better to also add info about how to set the property sheet to docs?