X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=README;h=61f40b5f90fcebef36fba46fda9961b369571c7d;hb=2eb952ca31aa13d1f6f429305fbb6f43a9a28c56;hp=06f0d3790d4b696e01788a277148250e4240068e;hpb=7af708a603390595e3988d7d461cf3e2f7db1797;p=PuTTY.git

diff --git a/README b/README
index 06f0d379..61f40b5f 100644
--- a/README
+++ b/README
@@ -3,7 +3,7 @@ and Unix Telnet and SSH client.
 
 If you want to rebuild PuTTY from source, we provide a variety of
 Makefiles and equivalents. (If you have fetched the source from
-Subversion, you'll have to generate the Makefiles yourself -- see
+Git, you'll have to generate the Makefiles yourself -- see
 below.)
 
 There are various compile-time directives that you can use to
@@ -40,7 +40,7 @@ For building on Windows:
    Makefile.bor' while in the `windows' subdirectory to build all
    the PuTTY binaries.
 
- - windows/Makefile.cyg is for Cygwin / mingw32 installations. Type
+ - windows/Makefile.cyg is for Cygwin / MinGW installations. Type
    `make -f Makefile.cyg' while in the `windows' subdirectory to
    build all the PuTTY binaries.
 
@@ -65,8 +65,12 @@ For building on Unix:
 
  - unix/configure is for Unix and GTK. If you don't have GTK, you
    should still be able to build the command-line utilities (PSCP,
-   PSFTP, Plink, PuTTYgen) using this script. To use it, change
-   into the `unix' subdirectory, run `./configure' and then `make'.
+   PSFTP, Plink, PuTTYgen) using this script. To use it, change into
+   the `unix' subdirectory, run `./configure' and then `make'. Or you
+   can do the same in the top-level directory (we provide a little
+   wrapper that invokes configure one level down), which is more like
+   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
@@ -99,9 +103,13 @@ For building on Unix:
 
  - The Unix Makefiles have an `install' target. Note that by default
    it tries to install `man' pages; if you have fetched the source via
-   Subversion then you will need to have built these using Halibut
+   Git then you will need to have built these using Halibut
    first - see below.
 
+ - It's also possible to build the Windows version of PuTTY to run
+   on Unix by using Winelib.  To do this, change to the `windows'
+   directory and run `make -f Makefile.cyg CC=winegcc RC=wrc'.
+
 All of the Makefiles are generated automatically from the file
 `Recipe' by the Perl script `mkfiles.pl' (except for the Unix one,
 which is generated by the `configure' script; mkfiles.pl only
@@ -111,7 +119,7 @@ corrections to the actual Makefiles, Makefile.am or Makefile.in.
 
 The Unix `configure' script and its various requirements are generated
 by the shell script `mkauto.sh', which requires GNU Autoconf, GNU
-Automake, and Gtk; if you've got the source from Subversion rather
+Automake, and Gtk; if you've got the source from Git rather
 than using one of our source snapshots, you'll need to run this
 yourself. The input file to Automake is generated by mkfiles.pl along
 with all the rest of the makefiles, so you will need to run mkfiles.pl