| 1 |
|
| 2 |
1. Download and install the MinGW compiler tools from www.mingw.org.
|
| 3 |
|
| 4 |
mingw32-make-3.80.0-3.exe
|
| 5 |
binutils-2.16.91-20060119-1.tar.gz
|
| 6 |
gcc-core-3.4.5-20060117-1.tar.gz
|
| 7 |
mingw-runtime-3.9.tar.gz
|
| 8 |
w32api-3.6.tar.gz
|
| 9 |
|
| 10 |
I installed these files into C:\MinGW, meaning I had to add C:\MinGW\bin
|
| 11 |
to my PATH.
|
| 12 |
|
| 13 |
You'll also need the HtmlHelp SDK from Microsoft so you can build
|
| 14 |
integrated CHM help. The HTMLHelp SDK available from
|
| 15 |
<http://go.microsoft.com/fwlink/?linkid=14188>
|
| 16 |
It normally installs into "C:\Program Files\HTML Help Workshop"
|
| 17 |
Add that to your PATH.
|
| 18 |
|
| 19 |
Optionally, to support multiple monitor displays, find multimon.h
|
| 20 |
and put it in the include path. The reliable way to find
|
| 21 |
multimon.h is to download the Microsoft Platform SDK and extract
|
| 22 |
from there. Once that is done, add this line to localconf.bat:
|
| 23 |
set multimon=
|
| 24 |
|
| 25 |
2. cd into putty/ and run mkfiles.pl once to generate the makefile(s).
|
| 26 |
|
| 27 |
You can do this on a unix host with Perl, or download and install perl
|
| 28 |
from http://www.activestate.com/Products/ActivePerl/ and run it from windows.
|
| 29 |
|
| 30 |
3. If you want to build MSI packages, you will need to download and install
|
| 31 |
the WiX core toolset from http://wix.sf.net/ - I install them into
|
| 32 |
C:\Program Files\Wix but if you have them elsewhere, set the variable WIXDIR
|
| 33 |
in localconf.bat (It is called by the build.bat script).
|
| 34 |
It will require the .NET framework (which you can get from
|
| 35 |
<http://go.microsoft.com/fwlink/?LinkId=17153>)
|
| 36 |
|
| 37 |
You might also want to install the Platform SDK from
|
| 38 |
<http://msdn.microsoft.com/library/en-us/msi/setup/
|
| 39 |
platform_sdk_components_for_windows_installer_developers.asp>
|
| 40 |
for packaging development, but it is optional.
|
| 41 |
|
| 42 |
4. Finally, on the build host, run the build.bat script. This will build the
|
| 43 |
packages and object files in a temporary build area (defaults to
|
| 44 |
%TEMP%/putty).
|
| 45 |
This split source-build directory approach speeds up development, but if
|
| 46 |
you don't like it, set builddir to the empty string or "./" in
|
| 47 |
localconf.bat.
|
| 48 |
|
| 49 |
If you are building from a subversion checkout, the revision number will be
|
| 50 |
automatically detected. Otherwise, set the REVISION variable in localconf.bat
|
| 51 |
to something representative.
|
| 52 |
|
| 53 |
If you are external to Quest Software, please do not publish custom PuTTY
|
| 54 |
builds in such a way that an installation could be mistaken as an official
|
| 55 |
build by Quest Software.
|
Parent Directory
| 
Revision Log