##// END OF EJS Templates
admin-commands: move the chainsaw extension to the admin commands module...
admin-commands: move the chainsaw extension to the admin commands module Activating an extension is always a little bit of a chore and the long name, options and "chainsaw" bits are deterrent enough. This also allows us to help the discoverability for people looking for repo "administration" tools, with the widest semantic of "administration".

File last commit:

r49953:136e94ed default
r52396:d4095f7b stable
Show More
readme.rst
44 lines | 1.5 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:
* 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.
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 * Python 3.6+ (to run the ``packaging.py`` script)
Gregory Szorc
inno: script to automate building Inno installer...
r42019
Building
========
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 The ``packaging.py`` script automates the process of producing an Inno
installer. It manages fetching and configuring non-system dependencies
(such as gettext, and various Python packages). It can be run from a
basic cmd.exe Window (i.e. activating the MSBuildTools environment is
not required).
Gregory Szorc
inno: script to automate building Inno installer...
r42019
From the prompt, change to the Mercurial source directory. e.g.
``cd c:\src\hg``.
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 Next, invoke ``packaging.py`` to produce an Inno installer.::
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 \
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 inno --pyoxidizer-target x86_64-pc-windows-msvc
Gregory Szorc
inno: script to automate building Inno installer...
r42019
If everything runs as intended, dependencies will be fetched and
configured into the ``build`` sub-directory, Mercurial will be built,
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 and an installer placed in the ``dist`` sub-directory. The final line
of output should print the name of the generated installer.
Gregory Szorc
inno: script to automate building Inno installer...
r42019
Matt Harbison
packaging: drop python27 references from the Windows instructions...
r49971 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.