X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;ds=sidebyside;f=README;h=5b6d9cbcd55237f9dcdef65f8d9b873227c68e02;hb=49d2cf19accb059b3b68d1fc2b78e606a578c3e8;hp=8f2a7914f7fefeece06a433d20d955d3ffa82e7e;hpb=0227bfdbc7ff6ed8d7b1cf83bdbefa9e44e674a5;p=PuTTY.git
diff --git a/README b/README
index 8f2a7914..5b6d9cbc 100644
--- a/README
+++ b/README
@@ -12,6 +12,9 @@ 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
+ the Platform SDK.
+
(We've also had one report of success building with the
OpenWatcom compiler -- www.openwatcom.org -- using Makefile.vc
with `wmake -ms -f makefile.vc' and NO_MULTIMON, although we
@@ -40,35 +43,47 @@ For building on Windows:
Makefile.lcc' while in the `windows' subdirectory. (You will
probably need to specify COMPAT=-DNO_MULTIMON.)
+ - Inside the windows/DEVCPP subdirectory are Dev-C++ project
+ files for doing GUI-based builds of the various PuTTY utilities.
+
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'.
+
+ 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 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.
+ -f Makefile.gtk'.
- For the graphical utilities, Gtk+-1.2 is required. Gtk+-2.0 is not
+ - For the graphical utilities, Gtk+-1.2 is required. Gtk+-2.0 is not
yet supported.
- There is an `install' target; note that by default it tries to
- install `man' pages, which need to be built using Halibut first --
- see below.
+ - Both Unix Makefiles have an `install' target. Note that by default
+ it tries to install `man' pages, which you may need to have built
+ using Halibut first -- see below.
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.
+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
+than using one of our source snapshots, you'll need to run this
+yourself.
+
Documentation (in various formats including Windows Help and Unix
-`man' pages) is to be built from the Halibut (`.but') files in the
-`doc' subdirectory using `doc/Makefile'. Halibut can be found at
-.
+`man' pages) is built from the Halibut (`.but') files in the `doc'
+subdirectory using `doc/Makefile'. If you aren't using one of our
+source snapshots, you'll need to do this yourself. Halibut can be
+found at .
The PuTTY home web site is