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