Differences between revisions 19 and 22 (spanning 3 versions)
Revision 19 as of 2007-08-26 05:24:46
Size: 1973
Editor: 220
Comment:
Revision 22 as of 2008-01-03 10:01:19
Size: 3210
Editor: abuehl
Comment: Added to CategoryWindows
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
      http://www.python.org/ftp/python/2.4.1/python-2.4.1.msi       http://www.python.org/ftp/python/2.4.3/python-2.4.3.msi
Line 21: Line 21:
patch.exe (from the gnuwin32 project or any other alternative)
      http://gnuwin32.sourceforge.net/packages/patch.htm
Line 27: Line 30:
ISTool ISTool ''(optional)''
Line 36: Line 39:
To build the html help files you need also:

asciidoc
      http://www.methods.co.nz/asciidoc/downloads.html

[Note: ''to configure it you have to adjust your path so the asciidoc.py file is found (I use a link to it from /bin in an msys install), and you have to change the CONF_DIR hardcoded into that file so the backend and help files are found (in my case it's changed to "C:/winp/msys/1.0/etc/asciidoc")'']
Line 43: Line 53:
python setup.py build -c mingw32 py2exe -b 1 python setup.py build -c mingw32
python setup.py
py2exe -b 1
Line 45: Line 56:

Note: the combined command "python setup.py build -c mingw32 py2exe -b 1" that had been suggested in the past doesn't work correctly, as it doesn't include the extensions in the mercurial subdirectory and separate commands should be used as indicated.
Line 52: Line 65:
which would allow you to ignore the {{{-c mingw32}}} option: which would allow you to skip the first build step and just run:
Line 57: Line 70:
Copy mfc71.dll and add_path.exe into the dist directory that just Copy mfc71.dll, add_path.exe and patch.exe into the dist directory that just
Line 59: Line 72:

To build the docs you:
{{{
cd doc
make html
cd ..
}}}
Line 66: Line 86:
file. file. In ISTool, type Ctrl-F9 to compile the installer file.
Line 68: Line 88:
In ISTool, type Ctrl-F9 to compile the installer file. The actual
installer will be in the C:\hg\hg-release\Output directory.
The actual installer will be in the C:\hg\hg-release\Output directory.

To automate the steps above you may want to create a batchfile based on the
following:
{{{
  echo [build] > setup.cfg
  echo compiler=mingw32 >> setup.cfg
  python setup.py py2exe -b 1
  iscc contrib\win32\mercurial.iss
}}}
and run it from the root of the hg repository (C:\hg\hg-release).

----
CategoryWindows

[Note: this page has been adapted from contrib/win32/win32-build.txt found in Mercurial's source tree]

The standalone Windows installer for Mercurial is built in a somewhat jury-rigged fashion.

Prerequisites

It has the following prerequisites, at least as I build it:

Python for Windows

MinGW

Python for Windows Extensions

mfc71.dll (just download, don't install)

patch.exe (from the gnuwin32 project or any other alternative)

The py2exe distutils extension

Inno Setup

ISTool (optional)

add_path (you need only add_path.exe in the zip file)

And, of course, Mercurial itself

To build the html help files you need also:

asciidoc

[Note: to configure it you have to adjust your path so the asciidoc.py file is found (I use a link to it from /bin in an msys install), and you have to change the CONF_DIR hardcoded into that file so the backend and help files are found (in my case it's changed to "C:/winp/msys/1.0/etc/asciidoc")]

Building Installer

Once you have all this installed and built, clone a copy of the Mercurial repository you want to package, and name the repo C:\hg\hg-release.

Open a command prompt window on C:\hg\hg-release, then build a standalone copy of the hg.exe program:

python setup.py build -c mingw32 
python setup.py py2exe -b 1

Note: the combined command "python setup.py build -c mingw32 py2exe -b 1" that had been suggested in the past doesn't work correctly, as it doesn't include the extensions in the mercurial subdirectory and separate commands should be used as indicated.

Alternatively, you can create a file named setup.cfg in the root of the repository (C:\hg\hg-release) with the following contents:

[build]
compiler=mingw32

which would allow you to skip the first build step and just run:

python setup.py py2exe -b 1

Copy mfc71.dll, add_path.exe and patch.exe into the dist directory that just got created.

To build the docs you:

cd doc
make html
cd ..

If Inno Setup is in your path you can run:

iscc contrib\win32\mercurial.iss

Or you can run ISTool, and open the C:\hg\hg-release\contrib\win32\mercurial.iss file. In ISTool, type Ctrl-F9 to compile the installer file.

The actual installer will be in the C:\hg\hg-release\Output directory.

To automate the steps above you may want to create a batchfile based on the following:

  echo [build] > setup.cfg
  echo compiler=mingw32 >> setup.cfg
  python setup.py py2exe -b 1
  iscc contrib\win32\mercurial.iss

and run it from the root of the hg repository (C:\hg\hg-release).


CategoryWindows

BuildingWindowsInstaller (last edited 2009-06-01 18:00:25 by PascalQuantin)