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
+Git, you'll have to generate the Makefiles yourself -- see
below.)
There are various compile-time directives that you can use to
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.)
+ As of 2016, we successfully compiled PuTTY with both Visual Studio
+ 7 (2003) and Visual Studio 14 (2015), so our guess is that it will
+ probably build with versions in between those as well.
- 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.
+ These have been tested on Visual Studio 7 and 10.
You should be able to build each PuTTY utility by loading the
corresponding .dsp file in Visual Studio. For example,
Makefile.bor' while in the `windows' subdirectory to build all
the PuTTY binaries.
- - windows/Makefile.cyg is for Cygwin / mingw32 installations. Type
+ - windows/Makefile.cyg is for Cygwin / MinGW installations. Type
`make -f Makefile.cyg' while in the `windows' subdirectory to
build all the PuTTY binaries.
a normal Unix source archive but doesn't do so well at keeping the
per-platform stuff in each platform's subdirectory; it's up to you.
- 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
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. If you have both installed, you can manually specify
- which one you want by giving the option '--with-gtk=1' or
- '--with-gtk=2' to the configure script. (2 is the default, of
- course.) In the absence of either, the configure script will
- automatically construct a Makefile which builds only the
- command-line utilities; you can manually create this condition by
- giving configure the option '--without-gtk'.
+ - For the graphical utilities, any of Gtk+-1.2, Gtk+-2.0, and Gtk+-3.0
+ should be supported. If you have more than one installed, you can
+ manually specify which one you want by giving the option
+ '--with-gtk=N' to the configure script where N is 1, 2, or 3.
+ (The default is the newest available, of course.) In the absence
+ of any Gtk version, the configure script will automatically
+ construct a Makefile which builds only the command-line utilities;
+ you can manually create this condition by giving configure the
+ option '--without-gtk'.
- pterm would like to be setuid or setgid, as appropriate, to permit
it to write records of user logins to /var/run/utmp and
- 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
+ Git then you will need to have built these using Halibut
first - see below.
+ - It's also possible to build the Windows version of PuTTY to run
+ on Unix by using Winelib. To do this, change to the `windows'
+ directory and run `make -f Makefile.cyg CC=winegcc RC=wrc'.
+
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
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
+Automake, and Gtk; if you've got the source from Git 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