##// END OF EJS Templates
packaging: replace a documentation reference to `python3` on Windows...
Matt Harbison -
r47179:e933e661 stable
parent child Browse files
Show More
@@ -1,61 +1,61 b''
1 1 Requirements
2 2 ============
3 3
4 4 Building the Inno installer requires a Windows machine.
5 5
6 6 The following system dependencies must be installed:
7 7
8 8 * Python 2.7 (download from https://www.python.org/downloads/)
9 9 * Microsoft Visual C++ Compiler for Python 2.7
10 10 (https://www.microsoft.com/en-us/download/details.aspx?id=44266)
11 11 * Inno Setup (http://jrsoftware.org/isdl.php) version 5.4 or newer.
12 12 Be sure to install the optional Inno Setup Preprocessor feature,
13 13 which is required.
14 14 * Python 3.5+ (to run the ``packaging.py`` script)
15 15
16 16 Building
17 17 ========
18 18
19 19 The ``packaging.py`` script automates the process of producing an
20 20 Inno installer. It manages fetching and configuring the
21 21 non-system dependencies (such as py2exe, gettext, and various
22 22 Python packages).
23 23
24 24 The script requires an activated ``Visual C++ 2008`` command prompt.
25 25 A shortcut to such a prompt was installed with ``Microsoft Visual C++
26 26 Compiler for Python 2.7``. From your Start Menu, look for
27 27 ``Microsoft Visual C++ Compiler Package for Python 2.7`` then launch
28 28 either ``Visual C++ 2008 32-bit Command Prompt`` or
29 29 ``Visual C++ 2008 64-bit Command Prompt``.
30 30
31 31 From the prompt, change to the Mercurial source directory. e.g.
32 32 ``cd c:\src\hg``.
33 33
34 34 Next, invoke ``packaging.py`` to produce an Inno installer. You will
35 35 need to supply the path to the Python interpreter to use.::
36 36
37 $ python3.exe contrib\packaging\packaging.py \
37 $ py -3 contrib\packaging\packaging.py \
38 38 inno --python c:\python27\python.exe
39 39
40 40 .. note::
41 41
42 42 The script validates that the Visual C++ environment is
43 43 active and that the architecture of the specified Python
44 44 interpreter matches the Visual C++ environment and errors
45 45 if not.
46 46
47 47 If everything runs as intended, dependencies will be fetched and
48 48 configured into the ``build`` sub-directory, Mercurial will be built,
49 49 and an installer placed in the ``dist`` sub-directory. The final
50 50 line of output should print the name of the generated installer.
51 51
52 52 Additional options may be configured. Run
53 53 ``packaging.py inno --help`` to see a list of program flags.
54 54
55 55 MinGW
56 56 =====
57 57
58 58 It is theoretically possible to generate an installer that uses
59 59 MinGW. This isn't well tested and ``packaging.py`` and may properly
60 60 support it. See old versions of this file in version control for
61 61 potentially useful hints as to how to achieve this.
@@ -1,71 +1,71 b''
1 1 WiX Installer
2 2 =============
3 3
4 4 The files in this directory are used to produce an MSI installer using
5 5 the WiX Toolset (http://wixtoolset.org/).
6 6
7 7 The MSI installers require elevated (admin) privileges due to the
8 8 installation of MSVC CRT libraries into the Windows system store. See
9 9 the Inno Setup installers in the ``inno`` sibling directory for installers
10 10 that do not have this requirement.
11 11
12 12 Requirements
13 13 ============
14 14
15 15 Building the WiX installers requires a Windows machine. The following
16 16 dependencies must be installed:
17 17
18 18 * Python 2.7 (download from https://www.python.org/downloads/)
19 19 * Microsoft Visual C++ Compiler for Python 2.7
20 20 (https://www.microsoft.com/en-us/download/details.aspx?id=44266)
21 21 * Python 3.5+ (to run the ``packaging.py`` script)
22 22
23 23 Building
24 24 ========
25 25
26 26 The ``packaging.py`` script automates the process of producing an MSI
27 27 installer. It manages fetching and configuring non-system dependencies
28 28 (such as py2exe, gettext, and various Python packages).
29 29
30 30 The script requires an activated ``Visual C++ 2008`` command prompt.
31 31 A shortcut to such a prompt was installed with ``Microsoft Visual
32 32 C++ Compiler for Python 2.7``. From your Start Menu, look for
33 33 ``Microsoft Visual C++ Compiler Package for Python 2.7`` then
34 34 launch either ``Visual C++ 2008 32-bit Command Prompt`` or
35 35 ``Visual C++ 2008 64-bit Command Prompt``.
36 36
37 37 From the prompt, change to the Mercurial source directory. e.g.
38 38 ``cd c:\src\hg``.
39 39
40 40 Next, invoke ``packaging.py`` to produce an MSI installer. You will need
41 41 to supply the path to the Python interpreter to use.::
42 42
43 $ python3 contrib\packaging\packaging.py \
43 $ py -3 contrib\packaging\packaging.py \
44 44 wix --python c:\python27\python.exe
45 45
46 46 .. note::
47 47
48 48 The script validates that the Visual C++ environment is active and
49 49 that the architecture of the specified Python interpreter matches the
50 50 Visual C++ environment. An error is raised otherwise.
51 51
52 52 If everything runs as intended, dependencies will be fetched and
53 53 configured into the ``build`` sub-directory, Mercurial will be built,
54 54 and an installer placed in the ``dist`` sub-directory. The final line
55 55 of output should print the name of the generated installer.
56 56
57 57 Additional options may be configured. Run ``packaging.py wix --help`` to
58 58 see a list of program flags.
59 59
60 60 Relationship to TortoiseHG
61 61 ==========================
62 62
63 63 TortoiseHG uses the WiX files in this directory.
64 64
65 65 The code for building TortoiseHG installers lives at
66 66 https://bitbucket.org/tortoisehg/thg-winbuild and is maintained by
67 67 Steve Borho (steve@borho.org).
68 68
69 69 When changing behavior of the WiX installer, be sure to notify
70 70 the TortoiseHG Project of the changes so they have ample time
71 71 provide feedback and react to those changes.
General Comments 0
You need to be logged in to leave comments. Login now