From 38de38907c2c4b0cefba9885d601fe859d3071f1 Mon Sep 17 00:00:00 2001 From: Elvin Aslanov Date: Tue, 28 Oct 2025 23:27:39 +0100 Subject: [PATCH 1/3] README.win32: Formatting Ease redability with text formatting using Pod's commands --- README.win32 | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/README.win32 b/README.win32 index 1f4d8534cd0d..0a5c7e32e020 100644 --- a/README.win32 +++ b/README.win32 @@ -14,7 +14,7 @@ These are instructions for building Perl under Windows 7 and later. =head1 DESCRIPTION -Before you start, you should glance through the README file +Before you start, you should glance through the F file found in the top-level directory to which the Perl distribution was extracted. Make sure you read and understand the terms under which this software is being distributed. @@ -22,13 +22,13 @@ which this software is being distributed. Also make sure you read L below for the known limitations of this port. -The INSTALL file in the perl top-level has much information that is +The F file in the perl top-level has much information that is only relevant to people building Perl on Unix-like systems. In particular, you can safely ignore any information that talks about -"Configure". +F. You may also want to look at one other option for building a perl that -will work on Windows: the README.cygwin file, which give a different +will work on Windows: the F file, which give a different set of rules to build a perl for Windows. This method will probably enable you to build a more Unix-compatible perl, but you will also need to download and use various other build-time and run-time support @@ -59,7 +59,7 @@ Delivers gcc toolchain building 32-bit executables (which can be used both 32 an Delivers gcc toolchain targeting both 64-bit Windows and 32-bit Windows platforms (despite the project name "mingw-w64" they are not only 64-bit -oriented). They deliver the native gcc compilers and cross-compilers +oriented). They deliver the native GCC compilers and cross-compilers that are also supported by perl's makefile. =back @@ -74,9 +74,9 @@ down compiler (no java, or gfortran) suitable for building perl available at: L NOTE: If you're using a 32-bit compiler to build perl on a 64-bit Windows -operating system, then you should set the WIN64 environment variable to "undef". -Also, the trimmed down compiler only passes tests when USE_ITHREADS *= define -(as opposed to undef) and when the CFG *= Debug line is commented out. +operating system, then you should set the C environment variable to C. +Also, the trimmed down compiler only passes tests when C +(as opposed to C) and when the C line is commented out. This port fully supports MakeMaker (the set of modules that is used to build extensions to perl). Therefore, you should be @@ -197,7 +197,7 @@ The defaults in the C makefile are set up to build with MinGW/gcc. =item * Edit the F (or F, if you're using F) and change -the values of I and C. You can also enable various build +the values of C and C. You can also enable various build flags. These are explained in the makefiles. Note that it is generally not a good idea to try to build a C with @@ -253,7 +253,7 @@ is the most commonly launched program during the build and later testing. =head2 Testing Perl on Windows -Type "gmake test" (or "nmake test"). This will run most +Type C (or C). This will run most of the tests from the testsuite (many tests will be skipped). There should be no test failures. @@ -272,7 +272,7 @@ native "cmd.exe", or if you are building from a path that contains spaces. So don't do that. If you are running the tests from a emacs shell window, you may see -failures in op/stat.t. Run "gmake test-notty" in that case. +failures in F. Run C in that case. Furthermore, you should make sure that during C you do not have any GNU tool packages in your path: some toolkits like Unixutils @@ -291,7 +291,7 @@ Please report any other failures as described under L. =head2 Installation of Perl on Windows -Type "gmake install" ("nmake install"). This will +Type C (C). This will put the newly built perl and the libraries under whatever C points to in the Makefile. It will also install the pod documentation under C<$INST_TOP\$INST_VER\lib\pod> and HTML versions of the same From d0821130f16e0048f9986c0bf68088c7814d1128 Mon Sep 17 00:00:00 2001 From: Elvin Aslanov Date: Tue, 28 Oct 2025 23:27:39 +0100 Subject: [PATCH 2/3] README.win32: Formatting-only Ease readability with text formatting using Pod's commands --- README.win32 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.win32 b/README.win32 index 0a5c7e32e020..b41131ffaf1f 100644 --- a/README.win32 +++ b/README.win32 @@ -196,7 +196,7 @@ The defaults in the C makefile are set up to build with MinGW/gcc. =item * -Edit the F (or F, if you're using F) and change +Edit the F (or F, if you're using C) and change the values of C and C. You can also enable various build flags. These are explained in the makefiles. From 57dee27fa3320123df286d00e084fcdfc939f8ac Mon Sep 17 00:00:00 2001 From: Elvin Aslanov Date: Thu, 30 Oct 2025 22:09:20 +0100 Subject: [PATCH 3/3] README.win32: Formatting-only Enhance readability by formatting text using Pod commands --- .gitignore | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.gitignore b/.gitignore index b062d95ddd28..d1ad15ffe07e 100644 --- a/.gitignore +++ b/.gitignore @@ -212,3 +212,9 @@ GTAGS # Makefile generated by the MSWin32 Smoker /win32/smoke.mk +/.vs/perl5-fork/FileContentIndex/0b7c5a37-b1bd-485d-b871-0f8078b8b48d.vsidx +/.vs/perl5-fork/FileContentIndex/0686ddf1-fce9-4518-8811-2503a42fd069.vsidx +/.vs/perl5-fork/FileContentIndex/525e21a4-8891-4620-bec5-d5b07233ecf1.vsidx +/.vs/perl5-fork/FileContentIndex/70455d9e-14b9-42cb-a635-f18ec67327a9.vsidx +/.vs/perl5-fork/FileContentIndex/81af8fc8-97b3-4b33-9694-d4198e0010cb.vsidx +/.vs/perl5-fork/FileContentIndex/9edddc83-6c71-4e3c-a2b5-f69230320109.vsidx