README 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. PuTTY source code README
  2. ========================
  3. This is the README for the source code of PuTTY, a free Windows and
  4. Unix Telnet and SSH client.
  5. PuTTY is built using CMake <https://cmake.org/>. To compile in the
  6. simplest way (on any of Linux, Windows or Mac), the general method is
  7. to run these commands in the source directory:
  8. cmake .
  9. cmake --build .
  10. These commands will expect to find a usable compile toolchain on your
  11. path. So if you're building on Windows with MSVC, you'll need to make
  12. sure that the MSVC compiler (cl.exe) is on your path, by running one
  13. of the 'vcvars32.bat' setup scripts provided with the tools. Then the
  14. cmake commands above should work.
  15. To install in the simplest way on Linux or Mac:
  16. cmake --build . --target install
  17. On Unix, pterm would like to be setuid or setgid, as appropriate, to
  18. permit it to write records of user logins to /var/run/utmp and
  19. /var/log/wtmp. (Of course it will not use this privilege for
  20. anything else, and in particular it will drop all privileges before
  21. starting up complex subsystems like GTK.) The cmake install step
  22. doesn't attempt to add these privileges, so if you want user login
  23. recording to work, you should manually ch{own,grp} and chmod the
  24. pterm binary yourself after installation. If you don't do this,
  25. pterm will still work, but not update the user login databases.
  26. Documentation (in various formats including Windows Help and Unix
  27. `man' pages) is built from the Halibut (`.but') files in the `doc'
  28. subdirectory. If you aren't using one of our source snapshots,
  29. you'll need to do this yourself. Halibut can be found at
  30. <https://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
  31. The PuTTY home web site is
  32. https://www.chiark.greenend.org.uk/~sgtatham/putty/
  33. If you want to send bug reports or feature requests, please read the
  34. Feedback section of the web site before doing so. Sending one-line
  35. reports saying `it doesn't work' will waste your time as much as
  36. ours.
  37. See the file LICENCE for the licence conditions.