mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-09 17:38:00 +00:00
64150a5ef2
mkfiles.pl no longer generates a Makefile.in, but instead generates a Makefile.am on which mkauto.sh runs automake. This means that the autoconfigured makefile now does build-time dependency tracking (a standard feature of automake-generated makefiles), and is generally more like what Unix people will expect. Some of the old-style make command-line settings (VER=-DRELEASE=foo, XFLAGS=-DDEBUG) will still work; the COMPAT settings are better done by autoconfiguration, and my habitual 'XFLAGS="-g -O0"' for an easily debuggable build will actually not work any more because CFLAGS is specified _after_ XFLAGS, so I should instead write 'make CFLAGS=-O0' (-g is the default in automake, removed at 'make install' time). The new makefile will automatically degrade into one that builds the command-line tools only, in the case where GTK could not be found. In principle, therefore, it should be an adequate replacement for _both_ the static Unix makefiles, Makefile.gtk and Makefile.ux. I haven't actually retired those in this commit, but I'm pretty tempted. [originally from svn r9239]
132 lines
6.0 KiB
Plaintext
132 lines
6.0 KiB
Plaintext
This is the README for the source archive of PuTTY, a free Win32
|
|
and Unix Telnet and SSH client.
|
|
|
|
If you want to rebuild PuTTY from source, we provide a variety of
|
|
Makefiles and equivalents. (If you have fetched the source from
|
|
Subversion, you'll have to generate the Makefiles yourself -- see
|
|
below.)
|
|
|
|
There are various compile-time directives that you can use to
|
|
disable or modify certain features; it may be necessary to do this
|
|
in some environments. They are documented in `Recipe', and in
|
|
comments in many of the generated Makefiles.
|
|
|
|
For building on Windows:
|
|
|
|
- windows/Makefile.vc is for command-line builds on MS Visual C++
|
|
systems. Change into the `windows' subdirectory and type `nmake
|
|
-f Makefile.vc' to build all the PuTTY binaries.
|
|
|
|
Last time we checked, PuTTY built with vanilla VC7, or VC6 with
|
|
an up-to-date Platform SDK. (It might still be possible to build
|
|
with vanilla VC6, but you'll certainly have to remove some
|
|
functionality with directives such as NO_IPV6.)
|
|
|
|
(We've also had reports of success building with the
|
|
OpenWatcom compiler -- www.openwatcom.org -- using Makefile.vc
|
|
with `wmake -ms -f makefile.vc' and NO_MULTIMON, although we
|
|
haven't tried this ourselves. Version 1.3 is reported to work.)
|
|
|
|
- Inside the windows/MSVC subdirectory are MS Visual Studio project
|
|
files for doing GUI-based builds of the various PuTTY utilities.
|
|
These have been tested on Visual Studio 6.
|
|
|
|
You should be able to build each PuTTY utility by loading the
|
|
corresponding .dsp file in Visual Studio. For example,
|
|
MSVC/putty/putty.dsp builds PuTTY itself, MSVC/plink/plink.dsp
|
|
builds Plink, and so on.
|
|
|
|
- windows/Makefile.bor is for the Borland C compiler. Type `make -f
|
|
Makefile.bor' while in the `windows' subdirectory to build all
|
|
the PuTTY binaries.
|
|
|
|
- windows/Makefile.cyg is for Cygwin / mingw32 installations. Type
|
|
`make -f Makefile.cyg' while in the `windows' subdirectory to
|
|
build all the PuTTY binaries.
|
|
|
|
You'll probably need quite a recent version of the w32api package.
|
|
Note that by default the multiple monitor and HTML Help support are
|
|
excluded from the Cygwin build, since at the time of writing Cygwin
|
|
doesn't include the necessary headers.
|
|
|
|
- windows/Makefile.lcc is for lcc-win32. Type `make -f
|
|
Makefile.lcc' while in the `windows' subdirectory. (You will
|
|
probably need to specify COMPAT=-DNO_MULTIMON.)
|
|
|
|
- Inside the windows/DEVCPP subdirectory are Dev-C++ project
|
|
files for doing GUI-based builds of the various PuTTY utilities.
|
|
|
|
The PuTTY team actively use Makefile.vc (with VC7) and Makefile.cyg
|
|
(with mingw32), so we'll probably notice problems with those
|
|
toolchains fairly quickly. Please report any problems with the other
|
|
toolchains mentioned above.
|
|
|
|
For building on Unix:
|
|
|
|
- unix/configure is for Unix and GTK. If you don't have GTK, you
|
|
should still be able to build the command-line utilities (PSCP,
|
|
PSFTP, Plink, PuTTYgen) using this script. To use it, change
|
|
into the `unix' subdirectory, run `./configure' and then `make'.
|
|
|
|
Note that Unix PuTTY has mostly only been tested on Linux so far;
|
|
portability problems such as BSD-style ptys or different header file
|
|
requirements are expected.
|
|
|
|
- unix/Makefile.gtk and unix/Makefile.ux are for non-autoconfigured
|
|
builds. These makefiles expect you to change into the `unix'
|
|
subdirectory, then run `make -f Makefile.gtk' or `make -f
|
|
Makefile.ux' respectively. Makefile.gtk builds all the programs but
|
|
relies on Gtk, whereas Makefile.ux builds only the command-line
|
|
utilities and has no Gtk dependence.
|
|
|
|
- For the graphical utilities, Gtk+-1.2 and Gtk+-2.0 should both be
|
|
supported. In the absence of either, the configure script will
|
|
automatically construct a Makefile which builds only the
|
|
command-line utilities.
|
|
|
|
- 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.) By default the makefile
|
|
will not attempt to add privileges to the pterm executable at 'make
|
|
install' time, but you can ask it to do so by running configure
|
|
with the option '--enable-setuid=USER' or '--enable-setgid=GROUP'.
|
|
|
|
- The Unix Makefiles have an `install' target. Note that by default
|
|
it tries to install `man' pages; if you have fetched the source via
|
|
Subversion then you will need to have built these using Halibut
|
|
first - see below.
|
|
|
|
All of the Makefiles are generated automatically from the file
|
|
`Recipe' by the Perl script `mkfiles.pl' (except for the Unix one,
|
|
which is generated by the `configure' script; mkfiles.pl only
|
|
generates the input to automake). Additions and corrections to Recipe,
|
|
mkfiles.pl and/or configure.ac are much more useful than additions and
|
|
corrections to the actual Makefiles, Makefile.am or Makefile.in.
|
|
|
|
The Unix `configure' script and its various requirements are generated
|
|
by the shell script `mkauto.sh', which requires GNU Autoconf, GNU
|
|
Automake, and Gtk; if you've got the source from Subversion rather
|
|
than using one of our source snapshots, you'll need to run this
|
|
yourself. The input file to Automake is generated by mkfiles.pl along
|
|
with all the rest of the makefiles, so you will need to run mkfiles.pl
|
|
and then mkauto.sh.
|
|
|
|
Documentation (in various formats including Windows Help and Unix
|
|
`man' pages) is built from the Halibut (`.but') files in the `doc'
|
|
subdirectory using `doc/Makefile'. If you aren't using one of our
|
|
source snapshots, you'll need to do this yourself. Halibut can be
|
|
found at <http://www.chiark.greenend.org.uk/~sgtatham/halibut/>.
|
|
|
|
The PuTTY home web site is
|
|
|
|
http://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.
|