Mercurial > hg
comparison contrib/packaging/inno/readme.rst @ 49080:b44678aeb460
packaging: drop python27 references from the Windows instructions
I also diffed these two files and eliminated cosmetic differences to make it
easier to ensure both are in alignment.
Differential Revision: https://phab.mercurial-scm.org/D12570
author | Matt Harbison <matt_harbison@yahoo.com> |
---|---|
date | Mon, 18 Apr 2022 16:11:52 -0400 |
parents | e933e66153f3 |
children | 905bc9d0a149 |
comparison
equal
deleted
inserted
replaced
49079:f40fb4c52594 | 49080:b44678aeb460 |
---|---|
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/) | |
9 * Microsoft Visual C++ Compiler for Python 2.7 | |
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. | 8 * Inno Setup (http://jrsoftware.org/isdl.php) version 5.4 or newer. |
12 Be sure to install the optional Inno Setup Preprocessor feature, | 9 Be sure to install the optional Inno Setup Preprocessor feature, |
13 which is required. | 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 Building | 13 Building |
17 ======== | 14 ======== |
18 | 15 |
19 The ``packaging.py`` script automates the process of producing an | 16 The ``packaging.py`` script automates the process of producing an Inno |
20 Inno installer. It manages fetching and configuring the | 17 installer. It manages fetching and configuring non-system dependencies |
21 non-system dependencies (such as py2exe, gettext, and various | 18 (such as gettext, and various Python packages). It can be run from a |
22 Python packages). | 19 basic cmd.exe Window (i.e. activating the MSBuildTools environment is |
23 | 20 not required). |
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``. | |
30 | 21 |
31 From the prompt, change to the Mercurial source directory. e.g. | 22 From the prompt, change to the Mercurial source directory. e.g. |
32 ``cd c:\src\hg``. | 23 ``cd c:\src\hg``. |
33 | 24 |
34 Next, invoke ``packaging.py`` to produce an Inno installer. You will | 25 Next, invoke ``packaging.py`` to produce an Inno installer.:: |
35 need to supply the path to the Python interpreter to use.:: | |
36 | 26 |
37 $ py -3 contrib\packaging\packaging.py \ | 27 $ py -3 contrib\packaging\packaging.py \ |
38 inno --python c:\python27\python.exe | 28 inno --pyoxidizer-target x86_64-pc-windows-msvc |
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. | |
46 | 29 |
47 If everything runs as intended, dependencies will be fetched and | 30 If everything runs as intended, dependencies will be fetched and |
48 configured into the ``build`` sub-directory, Mercurial will be built, | 31 configured into the ``build`` sub-directory, Mercurial will be built, |
49 and an installer placed in the ``dist`` sub-directory. The final | 32 and an installer placed in the ``dist`` sub-directory. The final line |
50 line of output should print the name of the generated installer. | 33 of output should print the name of the generated installer. |
51 | 34 |
52 Additional options may be configured. Run | 35 Additional options may be configured. Run ``packaging.py inno --help`` |
53 ``packaging.py inno --help`` to see a list of program flags. | 36 to see a list of program flags. |
54 | 37 |
55 MinGW | 38 MinGW |
56 ===== | 39 ===== |
57 | 40 |
58 It is theoretically possible to generate an installer that uses | 41 It is theoretically possible to generate an installer that uses |