mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-04-11 08:08:06 -05:00
7e8be5a204
During the transition to cmake, commit b00e5fb12929da5 renamed unix/unix.h to unix/platform.h, and for visual consistency, also renamed the guard macro PUTTY_UNIX_H to PUTTY_UNIX_PLATFORM_H. But I had failed to notice that that guard macro is re-tested in settings.c, as a convenient method of knowing whether we're building the Windows or Unix version of PuTTY in order to store some settings differently. So all those '#ifdef PUTTY_UNIX_H' statements silently became equivalent to '#if 0', because PUTTY_UNIX_H is _never_ defined any more. Specifically, these ifdefs were causing the time intervals relating to bell overloads to be off by a factor of 1000, because for some reason I can't remember, we were storing those intervals using a different time unit on Unix and Windows. In my own configuration, for example, ~/.putty/sessions/Default%20Settings contains "BellOverloadT=2000000" and "BellOverloadS=5000000", which originally meant that too many bells within 2 seconds would silence the bell until there were 5 seconds of silence - but current PuTTY shows it in the configurer as 2000 and 5000 seconds! This commit belatedly rewrites the ifdefs in settings.c, so that saved sessions from before 0.77 will now be interpreted correctly. Saved sessions from after that may need a rewrite. (But you have to have one or the other.) (cherry picked from commit 62b69a4f16875e75ece3c06fbe474104c5b5c089)
This is the README for PuTTY, a free Windows and Unix Telnet and SSH
client.
PuTTY is built using CMake <https://cmake.org/>. To compile in the
simplest way (on any of Linux, Windows or Mac), run these commands in
the source directory:
cmake .
cmake --build .
Then, to install in the simplest way on Linux or Mac:
cmake --build . --target install
On Unix, pterm would like to be setuid or setgid, as appropriate, to
permit it to write records of user logins to /var/run/utmp and
/var/log/wtmp. (Of course it will not use this privilege for
anything else, and in particular it will drop all privileges before
starting up complex subsystems like GTK.) The cmake install step
doesn't attempt to add these privileges, so if you want user login
recording to work, you should manually ch{own,grp} and chmod the
pterm binary yourself after installation. If you don't do this,
pterm will still work, but not update the user login databases.
Documentation (in various formats including Windows Help and Unix
`man' pages) is built from the Halibut (`.but') files in the `doc'
subdirectory. If you aren't using one of our source snapshots,
you'll need to do this yourself. Halibut can be found at
<https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
The PuTTY home web site is
https://www.chiark.greenend.org.uk/~sgtatham/putty/
If you want to send bug reports or feature requests, please read the
Feedback section of the web site before doing so. Sending one-line
reports saying `it doesn't work' will waste your time as much as
ours.
See the file LICENCE for the licence conditions.