| | 1 | This is the README for the source archive of PuTTY, a free Win32 |
| | 2 | and Unix Telnet and SSH client. |
| | 3 | |
| | 4 | If you want to rebuild PuTTY from source, we provide a variety of |
| | 5 | Makefiles and equivalents. (If you have fetched the source from |
| | 6 | Subversion, you'll have to generate the Makefiles yourself -- see |
| | 7 | below.) |
| | 8 | |
| | 9 | There are various compile-time directives that you can use to |
| | 10 | disable or modify certain features; it may be necessary to do this |
| | 11 | in some environments. They are documented in `Recipe', and in |
| | 12 | comments in many of the generated Makefiles. |
| | 13 | |
| | 14 | For building on Windows: |
| | 15 | |
| | 16 | - windows/Makefile.vc is for command-line builds on MS Visual C++ |
| | 17 | systems. Change into the `windows' subdirectory and type `nmake |
| | 18 | -f Makefile.vc' to build all the PuTTY binaries. |
| | 19 | |
| | 20 | Last time we checked, PuTTY built with vanilla VC7, or VC6 with |
| | 21 | the Platform SDK. |
| | 22 | |
| | 23 | (We've also had one report of success building with the |
| | 24 | OpenWatcom compiler -- www.openwatcom.org -- using Makefile.vc |
| | 25 | with `wmake -ms -f makefile.vc' and NO_MULTIMON, although we |
| | 26 | haven't tried this ourselves.) |
| | 27 | |
| | 28 | - Inside the windows/MSVC subdirectory are MS Visual Studio project |
| | 29 | files for doing GUI-based builds of the various PuTTY utilities. |
| | 30 | These have been tested on Visual Studio 6. |
| | 31 | |
| | 32 | You should be able to build each PuTTY utility by loading the |
| | 33 | corresponding .dsp file in Visual Studio. For example, |
| | 34 | MSVC/putty/putty.dsp builds PuTTY itself, MSVC/plink/plink.dsp |
| | 35 | builds Plink, and so on. |
| | 36 | |
| | 37 | - windows/Makefile.bor is for the Borland C compiler. Type `make -f |
| | 38 | Makefile.bor' while in the `windows' subdirectory to build all |
| | 39 | the PuTTY binaries. |
| | 40 | |
| | 41 | - windows/Makefile.cyg is for Cygwin / mingw32 installations. Type |
| | 42 | `make -f Makefile.cyg' while in the `windows' subdirectory to |
| | 43 | build all the PuTTY binaries. Note that by default the multiple |
| | 44 | monitor support is excluded from the Cygwin build, since at the |
| | 45 | time of writing Cygwin doesn't include the necessary headers. |
| | 46 | |
| | 47 | - windows/Makefile.lcc is for lcc-win32. Type `make -f |
| | 48 | Makefile.lcc' while in the `windows' subdirectory. (You will |
| | 49 | probably need to specify COMPAT=-DNO_MULTIMON.) |
| | 50 | |
| | 51 | - Inside the windows/DEVCPP subdirectory are Dev-C++ project |
| | 52 | files for doing GUI-based builds of the various PuTTY utilities. |
| | 53 | |
| | 54 | For building on Unix: |
| | 55 | |
| | 56 | - unix/configure is for Unix and GTK. If you don't have GTK, you |
| | 57 | should still be able to build the command-line utilities (PSCP, |
| | 58 | PSFTP, Plink, PuTTYgen) using this script. To use it, change |
| | 59 | into the `unix' subdirectory, run `./configure' and then `make'. |
| | 60 | |
| | 61 | Note that Unix PuTTY has mostly only been tested on Linux so far; |
| | 62 | portability problems such as BSD-style ptys or different header file |
| | 63 | requirements are expected. |
| | 64 | |
| | 65 | - unix/Makefile.gtk is for non-autoconfigured builds. This makefile |
| | 66 | expects you to change into the `unix' subdirectory, then run `make |
| | 67 | -f Makefile.gtk'. |
| | 68 | |
| | 69 | - For the graphical utilities, Gtk+-1.2 is required. Gtk+-2.0 is not |
| | 70 | yet supported. |
| | 71 | |
| | 72 | - Both Unix Makefiles have an `install' target. Note that by default |
| | 73 | it tries to install `man' pages, which you may need to have built |
| | 74 | using Halibut first -- see below. |
| | 75 | |
| | 76 | All of the Makefiles are generated automatically from the file |
| | 77 | `Recipe' by the Perl script `mkfiles.pl'. Additions and corrections |
| | 78 | to Recipe and the mkfiles.pl are much more useful than additions and |
| | 79 | corrections to the alternative Makefiles themselves. |
| | 80 | |
| | 81 | The Unix `configure' script and its various requirements are generated |
| | 82 | by the shell script `mkauto.sh', which requires GNU Autoconf, GNU |
| | 83 | Automake, and Gtk; if you've got the source from Subversion rather |
| | 84 | than using one of our source snapshots, you'll need to run this |
| | 85 | yourself. |
| | 86 | |
| | 87 | Documentation (in various formats including Windows Help and Unix |
| | 88 | `man' pages) is built from the Halibut (`.but') files in the `doc' |
| | 89 | subdirectory using `doc/Makefile'. If you aren't using one of our |
| | 90 | source snapshots, you'll need to do this yourself. Halibut can be |
| | 91 | found at <http://www.chiark.greenend.org.uk/~sgtatham/halibut/>. |
| | 92 | |
| | 93 | The PuTTY home web site is |
| | 94 | |
| | 95 | http://www.chiark.greenend.org.uk/~sgtatham/putty/ |
| | 96 | |
| | 97 | If you want to send bug reports or feature requests, please read the |
| | 98 | Feedback section of the web site before doing so. Sending one-line |
| | 99 | reports saying `it doesn't work' will waste your time as much as |
| | 100 | ours. |
| | 101 | |
| | 102 | See the file LICENCE for the licence conditions. |
projects / u / mdw / putty / blame_incremental