winsftp.c needs winsecur.h for process protection.

[PuTTY.git] / README

diff --git a/README b/README
index efa8941cd6630d1eabcaec609384c5a81f52e96a..10bd626156df6a2bfbd58db339d463d893a4b66d 100644 (file)
--- a/README
+++ b/README
@@ -17,19 +17,13 @@ For building on Windows:
    systems. Change into the `windows' subdirectory and type `nmake
    -f Makefile.vc' to build all the PuTTY binaries.
 
    systems. Change into the `windows' subdirectory and type `nmake
    -f Makefile.vc' to build all the PuTTY binaries.
 

-   Last time we checked, PuTTY built with vanilla VC7, or VC6 with
-   an up-to-date Platform SDK. (It might still be possible to build
-   with vanilla VC6, but you'll certainly have to remove some
-   functionality with directives such as NO_IPV6.)
-
-   (We've also had reports of success building with the
-   OpenWatcom compiler -- www.openwatcom.org -- using Makefile.vc
-   with `wmake -ms -f makefile.vc' and NO_MULTIMON, although we
-   haven't tried this ourselves. Version 1.3 is reported to work.)
+   As of 2016, we successfully compiled PuTTY with both Visual Studio
+   7 (2003) and Visual Studio 14 (2015), so our guess is that it will
+   probably build with versions in between those as well.

 
  - Inside the windows/MSVC subdirectory are MS Visual Studio project
    files for doing GUI-based builds of the various PuTTY utilities.
 
  - Inside the windows/MSVC subdirectory are MS Visual Studio project
    files for doing GUI-based builds of the various PuTTY utilities.

-   These have been tested on Visual Studio 6.
+   These have been tested on Visual Studio 7 and 10.

 
    You should be able to build each PuTTY utility by loading the
    corresponding .dsp file in Visual Studio. For example,
 
    You should be able to build each PuTTY utility by loading the
    corresponding .dsp file in Visual Studio. For example,


@@ -72,10 +66,6 @@ For building on Unix:
    a normal Unix source archive but doesn't do so well at keeping the
    per-platform stuff in each platform's subdirectory; it's up to you.
 
    a normal Unix source archive but doesn't do so well at keeping the
    per-platform stuff in each platform's subdirectory; it's up to you.
 

-   Note that Unix PuTTY has mostly only been tested on Linux so far;
-   portability problems such as BSD-style ptys or different header file
-   requirements are expected.
-

  - unix/Makefile.gtk and unix/Makefile.ux are for non-autoconfigured
    builds. These makefiles expect you to change into the `unix'
    subdirectory, then run `make -f Makefile.gtk' or `make -f
  - unix/Makefile.gtk and unix/Makefile.ux are for non-autoconfigured
    builds. These makefiles expect you to change into the `unix'
    subdirectory, then run `make -f Makefile.gtk' or `make -f