зеркало из https://github.com/github/putty.git
0d5d39064a
[originally from svn r516] |
||
---|---|---|
.cvsignore | ||
LICENCE | ||
MODULE | ||
Makefile | ||
README | ||
be_all.c | ||
be_none.c | ||
be_nossh.c | ||
ldisc.c | ||
misc.c | ||
mkfiles.pl | ||
mscrypto.c | ||
noise.c | ||
nosshres.rc | ||
putty.h | ||
putty.ico | ||
raw.c | ||
resource.h | ||
scp.c | ||
scp.h | ||
scp.ico | ||
scp.rc | ||
sizetip.c | ||
ssh.c | ||
ssh.h | ||
sshblowf.c | ||
sshcrc.c | ||
sshdes.c | ||
sshmd5.c | ||
sshrand.c | ||
sshrsa.c | ||
sshsha.c | ||
telnet.c | ||
terminal.c | ||
version.c | ||
win_res.h | ||
win_res.rc | ||
windlg.c | ||
window.c | ||
xlat.c |
README
This is the README for PuTTY, a free Win32 Telnet and SSH client. The provided Makefile is for MS Visual C++ systems. Type `nmake' to build both putty.exe (the main program) and pscp.exe (an SCP client). The comment at the top of the Makefile gives extra build options you can use to build in limited Win32s compatibility, a hack to pass SSH through some types of firewall, and `official' version numbers. MS Visual Studio version 6 falls over on the nasty macros in ssh.c. This is a bug in Visual Studio. The culprit is the /ZI compiler option (debug info generation: Edit and Continue). To avoid this problem while compiling PuTTY under VS6, you should: - right-click ssh.c in the FileView - click Settings - select the C/C++ tab and the General category - under `Debug info:', select anything _other_ than `Program Database for Edit and Continue'. Alternatively disable the /ZI option, replacing it with a saner value, such as /Zi. For other compilers, some alternative Makefiles are provided. These Makefiles are generated automatically from the master `Makefile' by the Perl script `mkfiles.pl'. Additions and corrections to the script are more useful than additions and corrections to the alternative Makefiles themselves. The PuTTY home web site is http://www.chiark.greenend.org.uk/~sgtatham/putty/ Bug reports and feature requests should be sent to <putty-bugs@lists.tartarus.org>. PLEASE read the section on the web site about how to report bugs effectively. Do NOT send one-line reports saying `it doesn't work'! See the file LICENCE for the licence conditions.