[mq]: cfg-mk

[wget] / windows / README

diff --git a/windows/README b/windows/README
index 7f8d2bf7f41ff56e95c4a3e54d271c10cc99c5f5..9239cef842bc3d9d43a78aa65e777c31aaa0f10e 100644 (file)
--- a/windows/README
+++ b/windows/README
@@ -6,16 +6,18 @@ list of possible options.  Run it with the option corresponding to the
 compiler you intend to use to build Wget and follow the (brief)
 instructions printed on the screen.  The instructions bellow are for
 building Wget with Microsoft Visual C++ (MSVC); you may need to make
-appropriate substitutions for your compiler and build environment; 
-currently wget can be built at least with Visual Studio/.Net, the free 
-Borland compiler, and the free cygnus and mingw environments.
+appropriate substitutions for your compiler and build environment;
+currently wget can be built at least with Visual Studio/.Net, the free
+Borland compiler, and the free mingw environment.  The instructions do
+*not* apply to the Cygwin environment, on which Wget is built with the
+procedure described in the INSTALL file in the top-level directory.
 
 To build Wget with MSVC run configure.bat (in the main Wget directory)
 with the argument --msvc, and then run nmake.  At a certain point in time
-Wget exposed some compiler bugs in MSVC 5.0; later Wget started to 
-expose (at least http.c, retr.c) some other compiler bugs in MSVC 6.0 
-SP6 (cl.exe version 12) which could/can be worked around by compiling 
-completely without optimization or at least partially (by using 
+Wget exposed some compiler bugs in MSVC 5.0; later Wget started to
+expose (at least http.c, retr.c) some other compiler bugs in MSVC 6.0
+SP6 (cl.exe version 12) which could/can be worked around by compiling
+completely without optimization or at least partially (by using
 #pragma optimize("g",on) and "off" around offending functions).
 However, read the rest of this document before continuing.
 
@@ -30,7 +32,7 @@ and from out32dll (in the OpenSSL directory) the two needed libraries
 (libeay32.lib and ssleay32.lib) to
 "C:\Program Files\Microsoft Visual Studio\VC98\lib".  These locations
 aren't exactly the best but will get you started if you don't know where
-to place these headers and libraries, you should find similar paths for 
+to place these headers and libraries, you should find similar paths for
 later compiler versions. Usually at run-time some OpenSSL
 libraries (currently ssleay32.dll and libeay32.dll) will need to be
 available in your environment PATH.