Add '=cut' to silence POD formatting warning

[perl5.git] / README.win32

diff --git a/README.win32 b/README.win32
index 448e590..45b8af8 100644 (file)
--- a/README.win32
+++ b/README.win32
@@ -63,9 +63,8 @@ that are also supported by perl's makefile.
 =back
 
 The Microsoft Visual C++ compilers are also now being given away free. They
-are available as "Visual C++ 2013-2019 Community Edition" (and also as part of
-the ".NET Framework SDK") and are the same compilers that ship with "Visual
-C++ 2013-2019 Professional".
+are available as "Visual C++ 2013-2022 Community Edition" and are the same
+compilers that ship with "Visual C++ 2013-2022 Professional".
 
 Visual C++ 2013 is capable of B<targeting> XP and Windows Server 2003 but the
 build host requirement is Windows 7/Windows Server 2012. For more details see
@@ -73,7 +72,6 @@ https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2013-compatibility-v
 and
 https://docs.microsoft.com/en-us/visualstudio/productinfo/vs2013-sysrequirements-vs
 
-The Windows SDK can be downloaded from L<https://developer.microsoft.com/windows/downloads/sdk-archive>.
 The MinGW64 compiler is available at L<http://mingw-w64.org>.
 The latter is actually a cross-compiler targeting Win64. There's also a trimmed
 down compiler (no java, or gfortran) suitable for building perl available at:
@@ -96,8 +94,8 @@ See L</Usage Hints for Perl on Windows> below for general hints about this.
 =item Make
 
 You need a "make" program to build the sources.  If you are using
-Visual C++ or the Windows SDK tools, you can use nmake supplied with Visual C++
-or Windows SDK. You may also use gmake instead of nmake.  Builds using gcc need
+Visual C++, you can use nmake supplied with Visual C++.
+You may also use gmake instead of nmake.  Builds using gcc need
 gmake. nmake is not supported for gcc builds.  Parallel building is only
 supported with gmake, not nmake.
 
@@ -129,19 +127,18 @@ console already set up for your target architecture (x86-32 or x86-64 or IA64).
 With the newer compilers, you may also use the older batch files if you choose
 so.
 
-=item Microsoft Visual C++ 2013-2019 Community Edition
+=item Microsoft Visual C++ 2013-2022 Community Edition
 
-These free versions of Visual C++ 2013-2019 Professional contain the same
+These free versions of Visual C++ 2013-2022 Professional contain the same
 compilers and linkers that ship with the full versions, and also contain
-everything necessary to build Perl, rather than requiring a separate download
-of the Windows SDK like previous versions did.
+everything necessary to build Perl.
 
 These packages can be downloaded by searching in the Download Center at
 L<https://www.microsoft.com/downloads/search.aspx?displaylang=en>.  (Providing exact
 links to these packages has proven a pointless task because the links keep on
 changing so often.)
 
-Install Visual C++ 2013-2019 Community, then setup your environment
+Install Visual C++ 2013-2022 Community, then setup your environment
 using, e.g.
 
  C:\Program Files\Microsoft Visual Studio 12.0\Common7\Tools\vsvars32.bat
@@ -149,13 +146,7 @@ using, e.g.
 (assuming the default installation location was chosen).
 
 Perl should now build using the win32/Makefile.  You will need to edit that
-file to set CCTYPE to one of MSVC90-MSVC142 first.
-
-=item Microsoft Platform SDK 64-bit Compiler
-
-The nmake that comes with the Platform SDK will suffice for building
-Perl.  Make sure you are building within one of the "Build Environment"
-shells available after you install the Platform SDK from the Start Menu.
+file to set CCTYPE to one of MSVC120-MSVC142 first.
 
 =item GCC
 
@@ -198,7 +189,7 @@ unlike GCC.
 
 Make sure you are in the "win32" subdirectory under the perl toplevel.
 This directory contains a "Makefile" that will work with
-versions of nmake that come with Visual C++ or the Windows SDK, and
+versions of nmake that come with Visual C++, and
 a GNU make "GNUmakefile" that will work for all supported compilers.
 The defaults in the gmake makefile are setup to build using MinGW/gcc.