delta/postgresql.git/src/tools/msvc/README, branch master git.postgresql.org: git/postgresql.git Remove support for Visual Studio 2013 2022-07-14T02:22:49+00:00 Michael Paquier michael@paquier.xyz 2022-07-14T02:22:49+00:00 6203583b72b58272010f8d06999811ff39922acf No members of the buildfarm are using this version of Visual Studio, resulting in all the code cleaned up here as being mostly dead, and VS2017 is the oldest version still supported. More versions could be cut, but the gain would be minimal, while removing only VS2013 has the advantage to remove from the core code all the dependencies on the value defined by _MSC_VER, where compatibility tweaks have accumulated across the years mostly around locales and strtof(), so that's a nice isolated cleanup. Note that this commit additionally allows a revert of 3154e16. The versions of Visual Studio now supported range from 2015 to 2022. Author: Michael Paquier Reviewed-by: Juan José Santamaría Flecha, Tom Lane, Thomas Munro, Justin Pryzby Discussion: https://postgr.es/m/YoH2IMtxcS3ncWn+@paquier.xyz 
No members of the buildfarm are using this version of Visual Studio,
resulting in all the code cleaned up here as being mostly dead, and
VS2017 is the oldest version still supported.

More versions could be cut, but the gain would be minimal, while
removing only VS2013 has the advantage to remove from the core code all
the dependencies on the value defined by _MSC_VER, where compatibility
tweaks have accumulated across the years mostly around locales and
strtof(), so that's a nice isolated cleanup.

Note that this commit additionally allows a revert of 3154e16.  The
versions of Visual Studio now supported range from 2015 to 2022.

Author: Michael Paquier
Reviewed-by: Juan José Santamaría Flecha, Tom Lane, Thomas Munro, Justin
Pryzby
Discussion: https://postgr.es/m/YoH2IMtxcS3ncWn+@paquier.xyz
Add support for Visual Studio 2022 in build scripts 2021-11-24T04:03:23+00:00 Michael Paquier michael@paquier.xyz 2021-11-24T04:03:23+00:00 b2265d305d81b0c1a2cec6c5b66a190a9e69e853 Documentation and any code paths related to VS are updated to keep the whole consistent. Similarly to 2017 and 2019, the version of VS and the version of nmake that we use to determine which code paths to use for the build are still inconsistent in their own way. Backpatch down to 10, so as buildfarm members are able to use this new version of Visual Studio on all the stable branches supported. Author: Hans Buschmann Discussion: https://postgr.es/m/1633101364685.39218@nidsa.net Backpatch-through: 10 
Documentation and any code paths related to VS are updated to keep the
whole consistent.  Similarly to 2017 and 2019, the version of VS and the
version of nmake that we use to determine which code paths to use for
the build are still inconsistent in their own way.

Backpatch down to 10, so as buildfarm members are able to use this new
version of Visual Studio on all the stable branches supported.

Author: Hans Buschmann
Discussion: https://postgr.es/m/1633101364685.39218@nidsa.net
Backpatch-through: 10
Fix typos and grammar in docs and comments 2020-12-24T08:05:49+00:00 Michael Paquier michael@paquier.xyz 2020-12-24T08:05:49+00:00 90fbf7c57df601c7e0b43ae7cf71f0f69908a7cc This fixes several areas of the documentation and some comments in matters of style, grammar, or even format. Author: Justin Pryzby Discussion: https://postgr.es/m/20201222041153.GK30237@telsasoft.com 
This fixes several areas of the documentation and some comments in
matters of style, grammar, or even format.

Author: Justin Pryzby
Discussion: https://postgr.es/m/20201222041153.GK30237@telsasoft.com
Add support for Visual Studio 2019 in build scripts 2019-07-02T05:02:33+00:00 Michael Paquier michael@paquier.xyz 2019-07-02T05:02:33+00:00 2b1394fc2b52a2573d08aa626e7b49568f27464e This fixes at the same time a set of inconsistencies in the documentation and the scripts related to the versions of Windows SDK supported. Author: Haribabu Kommi Reviewed-by: Andrew Dunstan, Juan José Santamaría Flecha, Michael Paquier Discussion: https://postgr.es/m/CAJrrPGcfqXhfPyMrny9apoDU7M1t59dzVAvoJ9AeAh5BJi+UzA@mail.gmail.com 
This fixes at the same time a set of inconsistencies in the
documentation and the scripts related to the versions of Windows SDK
supported.

Author: Haribabu Kommi
Reviewed-by: Andrew Dunstan, Juan José Santamaría Flecha, Michael
Paquier
Discussion: https://postgr.es/m/CAJrrPGcfqXhfPyMrny9apoDU7M1t59dzVAvoJ9AeAh5BJi+UzA@mail.gmail.com
Require C99 (and thus MSCV 2013 upwards). 2018-08-24T01:33:57+00:00 Andres Freund andres@anarazel.de 2018-08-24T01:33:40+00:00 d9dd406fe281d22d5238d3c26a7182543c711e74 In 86d78ef50e01 I enabled configure to check for C99 support, with the goal of checking which platforms support C99. While there are a few machines without C99 support among our buildfarm animals, de-supporting them for v12 was deemed acceptable. While not tested in aforementioned commit, the biggest increase in minimum compiler version comes from MSVC, which gained C99 support fairly late. The subset in MSVC 2013 is sufficient for our needs, at this point. While that is a significant increase in minimum version, the existing windows binaries are already built with a new enough version. Make configure error out if C99 support could not be detected. For MSVC builds, increase the minimum version to 2013. The increase to MSVC 2013 allows us to get rid of VCBuildProject.pm, as that was only required for MSVC 2005/2008. Author: Andres Freund Discussion: https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com 
In 86d78ef50e01 I enabled configure to check for C99 support, with the
goal of checking which platforms support C99.  While there are a few
machines without C99 support among our buildfarm animals,
de-supporting them for v12 was deemed acceptable.

While not tested in aforementioned commit, the biggest increase in
minimum compiler version comes from MSVC, which gained C99 support
fairly late. The subset in MSVC 2013 is sufficient for our needs, at
this point. While that is a significant increase in minimum version,
the existing windows binaries are already built with a new enough
version.

Make configure error out if C99 support could not be detected. For
MSVC builds, increase the minimum version to 2013.

The increase to MSVC 2013 allows us to get rid of VCBuildProject.pm,
as that was only required for MSVC 2005/2008.

Author: Andres Freund
Discussion: https://postgr.es/m/97d4b165-192d-3605-749c-f614a0c4e783@2ndquadrant.com
Remove obsolete documentation build tools for Windows 2018-07-13T08:01:04+00:00 Peter Eisentraut peter_e@gmx.net 2018-07-13T08:01:04+00:00 1f4ec8945967a75f711d721860752985624a0957 The scripts and instructions have been nonfunctional at least since PostgreSQL 10 (commit 510074f9f0131a04322d6a3d2a51c87e6db243f9) and nobody has stepped up to fix them. So right now just remove them until someone wants to resurrect them. Discussion: https://www.postgresql.org/message-id/flat/B74C0219-6BA9-46E1-A524-5B9E8CD3BDB3%40yesql.se 
The scripts and instructions have been nonfunctional at least since
PostgreSQL 10 (commit 510074f9f0131a04322d6a3d2a51c87e6db243f9) and
nobody has stepped up to fix them.  So right now just remove them until
someone wants to resurrect them.

Discussion: https://www.postgresql.org/message-id/flat/B74C0219-6BA9-46E1-A524-5B9E8CD3BDB3%40yesql.se
Support building with Visual Studio 2017 2017-09-25T12:03:05+00:00 Andrew Dunstan andrew@dunslane.net 2017-09-25T12:03:05+00:00 f2ab3898f3a25ef431db4ea90a8d128b974dbffe Haribabu Kommi, reviewed by Takeshi Ideriha and Christian Ullrich Backpatch to 9.6 
Haribabu Kommi, reviewed by Takeshi Ideriha and Christian Ullrich

Backpatch to 9.6
Enable building with Microsoft Visual Studio 2012. 2013-02-06T19:52:29+00:00 Andrew Dunstan andrew@dunslane.net 2013-02-06T19:52:29+00:00 e1c1e2173248f39c1b15fca7b2a31ad7b5199ce7 Backpatch to release 9.2 Brar Piening and Noah Misch, reviewed by Craig Ringer. 
Backpatch to release 9.2

Brar Piening and Noah Misch, reviewed by Craig Ringer.
Remove whitespace from end of lines 2012-05-15T19:19:41+00:00 Peter Eisentraut peter_e@gmx.net 2012-05-15T19:19:04+00:00 c8e086795a7ffc5244e03ffc2c92a3ae915a5055 pgindent and perltidy should clean up the rest. 
pgindent and perltidy should clean up the rest.
Lots of doc corrections. 2012-04-24T02:43:09+00:00 Robert Haas rhaas@postgresql.org 2012-04-24T02:43:09+00:00 5d4b60f2f25bedee257aaf6f2f4ac77028629b87 Josh Kupershmidt 
Josh Kupershmidt