##// END OF EJS Templates
windows-ci: run Windows CI automatically alongside the others...
windows-ci: run Windows CI automatically alongside the others This will enable us to make Windows Python 3 a first-class citizen for the next 6.0 cycle. We will probably get some flaky tests and we're missing others that are skipped, but we'll turn them on it future patches. Differential Revision: https://phab.mercurial-scm.org/D11256

File last commit:

r47179:e933e661 stable
r48611:f799a4b6 stable
Show More
readme.rst
61 lines | 2.2 KiB | text/x-rst | RstLexer
Gregory Szorc
inno: script to automate building Inno installer...
r42019 Requirements
============
Building the Inno installer requires a Windows machine.
The following system dependencies must be installed:
* Python 2.7 (download from https://www.python.org/downloads/)
* Microsoft Visual C++ Compiler for Python 2.7
(https://www.microsoft.com/en-us/download/details.aspx?id=44266)
* Inno Setup (http://jrsoftware.org/isdl.php) version 5.4 or newer.
Be sure to install the optional Inno Setup Preprocessor feature,
which is required.
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 * Python 3.5+ (to run the ``packaging.py`` script)
Gregory Szorc
inno: script to automate building Inno installer...
r42019
Building
========
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 The ``packaging.py`` script automates the process of producing an
Gregory Szorc
inno: script to automate building Inno installer...
r42019 Inno installer. It manages fetching and configuring the
non-system dependencies (such as py2exe, gettext, and various
Python packages).
The script requires an activated ``Visual C++ 2008`` command prompt.
A shortcut to such a prompt was installed with ``Microsoft Visual C++
Compiler for Python 2.7``. From your Start Menu, look for
``Microsoft Visual C++ Compiler Package for Python 2.7`` then launch
either ``Visual C++ 2008 32-bit Command Prompt`` or
``Visual C++ 2008 64-bit Command Prompt``.
From the prompt, change to the Mercurial source directory. e.g.
``cd c:\src\hg``.
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 Next, invoke ``packaging.py`` to produce an Inno installer. You will
Matt Harbison
inno: correct the path display in a literal block of the readme...
r42813 need to supply the path to the Python interpreter to use.::
Gregory Szorc
inno: script to automate building Inno installer...
r42019
Matt Harbison
packaging: replace a documentation reference to `python3` on Windows...
r47179 $ py -3 contrib\packaging\packaging.py \
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 inno --python c:\python27\python.exe
Gregory Szorc
inno: script to automate building Inno installer...
r42019
.. note::
The script validates that the Visual C++ environment is
active and that the architecture of the specified Python
interpreter matches the Visual C++ environment and errors
if not.
If everything runs as intended, dependencies will be fetched and
configured into the ``build`` sub-directory, Mercurial will be built,
and an installer placed in the ``dist`` sub-directory. The final
line of output should print the name of the generated installer.
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 Additional options may be configured. Run
``packaging.py inno --help`` to see a list of program flags.
Gregory Szorc
inno: script to automate building Inno installer...
r42019
MinGW
=====
It is theoretically possible to generate an installer that uses
Gregory Szorc
packaging: consolidate CLI functionality into packaging.py...
r43913 MinGW. This isn't well tested and ``packaging.py`` and may properly
Gregory Szorc
inno: script to automate building Inno installer...
r42019 support it. See old versions of this file in version control for
potentially useful hints as to how to achieve this.