mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-03-13 10:33:51 -05:00
b72c9aba28
This will replace the various pieces of Perl scattered throughout the code base in comments above long boring data tables. The idea is that those long boring tables will move into header files in the new 'unicode' directory, and will be #included from the source files that use the tables. One benefit is that I won't have to page tediously past the tables to get to the actual code I want to edit. But more importantly, it should now become easy to update to a new version of Unicode, by re-running just one script and committing the changed versions of all the headers in the 'unicode' subdir. This version of the script regenerates six Unicode-derived tables in the existing source code in a byte-for-byte identical form. In the next commits I'll clean it up, commit the output, and delete the tables from their previous locations. (One table I _haven't_ incorporated into this system is the Arabic shaping table in bidi.c, because my attempt to regenerate it came out not matching the original at all. That _might_ be because the table is based on an old Unicode standard and desperately needs updating, but it might also be because I misunderstood how it works. So I'll leave sorting that out for another time.)
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.