mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-05-28 23:34:49 -05:00
92eb0710e3
isn't configured to do it: we now have a sysmenu option for it. In addition, there's a special case such that clicking the top left pixel on the screen in full-screen mode brings up the sysmenu (so you can still get at the sysmenu in FS mode without Alt-anything configured to bring it up and without ghastly fiddling with the Windows key). Also Change Settings while in full-screen mode now adds/removes the scrollbar in response to scrollbar_in_fullscreen rather than scrollbar (oops). [originally from svn r1410]
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.