Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mRemoteNG/PuTTYNG.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorJacob Nevins <jacobn@chiark.greenend.org.uk>2005-05-23 16:41:21 +0400
committerJacob Nevins <jacobn@chiark.greenend.org.uk>2005-05-23 16:41:21 +0400
commit203a25d5021e195d0a90752cb4e7776715257217 (patch)
treeb5fdbf630171dc27083843616b8b8a5069a237d8 /README
parent99ecca53edf20e7190388a491bd1743457207cd5 (diff)
Miscellaneous updates:
- note Visual Foo version requirements - note which things are done for you in our source snapshots - other tweaks [originally from svn r5839]
Diffstat (limited to 'README')
-rw-r--r--README36
1 files changed, 23 insertions, 13 deletions
diff --git a/README b/README
index 991164e5..68eb2c8b 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
@@ -46,31 +49,38 @@ For building on Unix:
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.
+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
-<http://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
+`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 <http://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is