| 1 | This is the README for the source archive of PuTTY, a free Win32 |
| 2 | Telnet and SSH client. |
| 3 | |
| 4 | If you want to rebuild PuTTY from source, we provide a variety of |
| 5 | Makefiles and equivalents: |
| 6 | |
| 7 | - Makefile.vc is for command-line builds on MS Visual C++ systems. |
| 8 | Type `nmake -f Makefile.vc' to build all the PuTTY binaries. |
| 9 | |
| 10 | (We've also had one report of success building with the |
| 11 | OpenWatcom compiler -- www.openwatcom.org -- using Makefile.vc |
| 12 | with `wmake -ms -f makefile.vc' and NO_MULTIMON, although we |
| 13 | haven't tried this ourselves.) |
| 14 | |
| 15 | - Inside the MSVC subdirectory are MS Visual Studio project files |
| 16 | for doing GUI-based builds of the various PuTTY utilities. These |
| 17 | have been tested on Visual Studio 6. |
| 18 | |
| 19 | You should be able to build each PuTTY utility by loading the |
| 20 | corresponding .dsp file in Visual Studio. For example, |
| 21 | MSVC/putty/putty.dsp builds PuTTY itself, MSVC/plink/plink.dsp |
| 22 | builds Plink, and so on. |
| 23 | |
| 24 | - Makefile.bor is for the Borland C compiler. Type `make -f |
| 25 | Makefile.bor' to build all the PuTTY binaries. |
| 26 | |
| 27 | - Makefile.cyg is for Cygwin / mingw32 installations. Type `make -f |
| 28 | Makefile.cyg' to build all the PuTTY binaries. Note that by |
| 29 | default the Pageant WinNT security features and the multiple |
| 30 | monitor support are excluded from the Cygwin build, since at the |
| 31 | time of writing this Cygwin doesn't include the necessary |
| 32 | headers. |
| 33 | |
| 34 | All of the Makefiles are generated automatically from the file |
| 35 | `Recipe' by the Perl script `mkfiles.pl'. Additions and corrections |
| 36 | to Recipe and the mkfiles.pl are much more useful than additions and |
| 37 | corrections to the alternative Makefiles themselves. |
| 38 | |
| 39 | The PuTTY home web site is |
| 40 | |
| 41 | http://www.chiark.greenend.org.uk/~sgtatham/putty/ |
| 42 | |
| 43 | If you want to send bug reports or feature requests, please read the |
| 44 | Feedback section of the web site before doing so. Sending one-line |
| 45 | reports saying `it doesn't work' will waste your time as much as |
| 46 | ours. |
| 47 | |
| 48 | See the file LICENCE for the licence conditions. |