X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=README;h=10bd626156df6a2bfbd58db339d463d893a4b66d;hb=145ecf611238c4f1e39d89d3eee40319a2c54fe8;hp=61f40b5f90fcebef36fba46fda9961b369571c7d;hpb=09111ea9c27c5f0c2d66866294f3ad9bfc08db9f;p=PuTTY.git

diff --git a/README b/README
index 61f40b5f..10bd6261 100644
--- 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.
 
-   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.
-   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,
@@ -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.
 
-   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
@@ -83,14 +73,15 @@ For building on Unix:
    relies on Gtk, whereas Makefile.ux builds only the command-line
    utilities and has no Gtk dependence.
 
- - For the graphical utilities, Gtk+-1.2 and Gtk+-2.0 should both be
-   supported. If you have both installed, you can manually specify
-   which one you want by giving the option '--with-gtk=1' or
-   '--with-gtk=2' to the configure script. (2 is the default, of
-   course.) In the absence of either, the configure script will
-   automatically construct a Makefile which builds only the
-   command-line utilities; you can manually create this condition by
-   giving configure the option '--without-gtk'.
+ - For the graphical utilities, any of Gtk+-1.2, Gtk+-2.0, and Gtk+-3.0
+   should be supported. If you have more than one installed, you can
+   manually specify which one you want by giving the option
+   '--with-gtk=N' to the configure script where N is 1, 2, or 3.
+   (The default is the newest available, of course.) In the absence
+   of any Gtk version, the configure script will automatically
+   construct a Makefile which builds only the command-line utilities;
+   you can manually create this condition by giving configure the
+   option '--without-gtk'.
 
  - pterm would like to be setuid or setgid, as appropriate, to permit
    it to write records of user logins to /var/run/utmp and