Move generation of the "configure" script into its own script so that

[u/mdw/putty] / README

diff --git a/README b/README
index e178791..991164e 100644 (file)
--- a/README
+++ b/README
@@ -42,11 +42,14 @@ For building on Windows:
 
 For building on Unix:
 
- - unix/Makefile.gtk is for Unix and GTK. If you don't have GTK, you
+ - 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 makefile. The makefile expects
-   you to change into the `unix' subdirectory, then run `make -f
-   Makefile.gtk'. Note that Unix PuTTY has mostly only been tested
+   PSFTP, Plink, PuTTYgen) using this script. To use it, change
+   into the `unix' subdirectory, run `./configure' and then `make'.
+ 
+ - unix/Makefile.gtk is for non-autoconfigured builds. This makefile
+   expects you to change into the `unix' subdirectory, then run `make
+   -f Makefile.gtk'. 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.
 
@@ -60,7 +63,9 @@ For building on Unix:
 All of the Makefiles are generated automatically from the file
 `Recipe' by the Perl script `mkfiles.pl'. Additions and corrections
 to Recipe and the mkfiles.pl are much more useful than additions and
-corrections to the alternative Makefiles themselves.
+corrections to the alternative Makefiles themselves. The Unix `configure'
+script and its various requirements are generated by the shell script
+`mkauto.sh', which requires GNU Autoconf, GNU Automake, and Gtk.
 
 Documentation (in various formats including Windows Help and Unix
 `man' pages) is to be built from the Halibut (`.but') files in the