##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

inno: correct the path display in a literal block of the readme...
Matt Harbison -
r42813:8f7c3f43 default
parent child Browse files
Show More
Show file before | Show file after | Hide comments
@@ -1,61 +1,61 b''
1 Requirements
1 Requirements
2 ============
2 ============
3
3
4 Building the Inno installer requires a Windows machine.
4 Building the Inno installer requires a Windows machine.
5
5
6 The following system dependencies must be installed:
6 The following system dependencies must be installed:
7
7
8 * Python 2.7 (download from https://www.python.org/downloads/)
8 * Python 2.7 (download from https://www.python.org/downloads/)
9 * Microsoft Visual C++ Compiler for Python 2.7
9 * Microsoft Visual C++ Compiler for Python 2.7
10 (https://www.microsoft.com/en-us/download/details.aspx?id=44266)
10 (https://www.microsoft.com/en-us/download/details.aspx?id=44266)
11 * Inno Setup (http://jrsoftware.org/isdl.php) version 5.4 or newer.
11 * Inno Setup (http://jrsoftware.org/isdl.php) version 5.4 or newer.
12 Be sure to install the optional Inno Setup Preprocessor feature,
12 Be sure to install the optional Inno Setup Preprocessor feature,
13 which is required.
13 which is required.
14 * Python 3.5+ (to run the ``build.py`` script)
14 * Python 3.5+ (to run the ``build.py`` script)
15
15
16 Building
16 Building
17 ========
17 ========
18
18
19 The ``build.py`` script automates the process of producing an
19 The ``build.py`` script automates the process of producing an
20 Inno installer. It manages fetching and configuring the
20 Inno installer. It manages fetching and configuring the
21 non-system dependencies (such as py2exe, gettext, and various
21 non-system dependencies (such as py2exe, gettext, and various
22 Python packages).
22 Python packages).
23
23
24 The script requires an activated ``Visual C++ 2008`` command prompt.
24 The script requires an activated ``Visual C++ 2008`` command prompt.
25 A shortcut to such a prompt was installed with ``Microsoft Visual C++
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
26 Compiler for Python 2.7``. From your Start Menu, look for
27 ``Microsoft Visual C++ Compiler Package for Python 2.7`` then launch
27 ``Microsoft Visual C++ Compiler Package for Python 2.7`` then launch
28 either ``Visual C++ 2008 32-bit Command Prompt`` or
28 either ``Visual C++ 2008 32-bit Command Prompt`` or
29 ``Visual C++ 2008 64-bit Command Prompt``.
29 ``Visual C++ 2008 64-bit Command Prompt``.
30
30
31 From the prompt, change to the Mercurial source directory. e.g.
31 From the prompt, change to the Mercurial source directory. e.g.
32 ``cd c:\src\hg``.
32 ``cd c:\src\hg``.
33
33
34 Next, invoke ``build.py`` to produce an Inno installer. You will
34 Next, invoke ``build.py`` to produce an Inno installer. You will
35 need to supply the path to the Python interpreter to use.:
35 need to supply the path to the Python interpreter to use.::
36
36
37 $ python3.exe contrib\packaging\inno\build.py \
37 $ python3.exe contrib\packaging\inno\build.py \
38 --python c:\python27\python.exe
38 --python c:\python27\python.exe
39
39
40 .. note::
40 .. note::
41
41
42 The script validates that the Visual C++ environment is
42 The script validates that the Visual C++ environment is
43 active and that the architecture of the specified Python
43 active and that the architecture of the specified Python
44 interpreter matches the Visual C++ environment and errors
44 interpreter matches the Visual C++ environment and errors
45 if not.
45 if not.
46
46
47 If everything runs as intended, dependencies will be fetched and
47 If everything runs as intended, dependencies will be fetched and
48 configured into the ``build`` sub-directory, Mercurial will be built,
48 configured into the ``build`` sub-directory, Mercurial will be built,
49 and an installer placed in the ``dist`` sub-directory. The final
49 and an installer placed in the ``dist`` sub-directory. The final
50 line of output should print the name of the generated installer.
50 line of output should print the name of the generated installer.
51
51
52 Additional options may be configured. Run ``build.py --help`` to
52 Additional options may be configured. Run ``build.py --help`` to
53 see a list of program flags.
53 see a list of program flags.
54
54
55 MinGW
55 MinGW
56 =====
56 =====
57
57
58 It is theoretically possible to generate an installer that uses
58 It is theoretically possible to generate an installer that uses
59 MinGW. This isn't well tested and ``build.py`` and may properly
59 MinGW. This isn't well tested and ``build.py`` and may properly
60 support it. See old versions of this file in version control for
60 support it. See old versions of this file in version control for
61 potentially useful hints as to how to achieve this.
61 potentially useful hints as to how to achieve this.
General Comments 0
You need to be logged in to leave comments. Login now