upstream/mercurial-mirror Files · contrib/packaging/inno/readme.rst

rust-matchers: add `Matcher` trait and implement `AlwaysMatcher`...

rust-matchers: add `Matcher` trait and implement `AlwaysMatcher` In our quest of a faster Mercurial, we have arrived at the point where we need to implement the matchers in Rust. This RFC mainly for the `Matcher` trait to see if the changes proposed feel fine to people with more experience on the matter. While the `AlwaysMatcher` implementation is here as a trivial example, it should be the first step towards matchers use in Rust as it is currently the only supported one. Notable changes: - `exact` is renamed to `exact_match` - enums for `visit*` methods with `Recursive` instead of `'all'`, etc. - a new `roots`, separate from `file_set` - no `bad`, `explicitdir` or `traversedir` functions as they can be passed to the high functions instead of the matchers Thanks to Martin for suggesting the last two (most important) changes and for reaching out to help a few weeks ago. Differential Revision: https://phab.mercurial-scm.org/D7178

Matt Harbison - - Load All Authors

File last commit:

r42813:8f7c3f43 default


                r43742:a77d4fe3

default

Download file

             readme.rst
        
                    61 lines
            
             | 2.2 KiB
            
                | text/x-rst
            
             |
                RstLexer
            
             / contrib / packaging / inno / readme.rst
          
                    History
                
                 |
                  Source
                 | Raw
                 |Copy content
                 |Copy permalink

        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.

      * Python 3.5+ (to run the ``build.py`` script)

      Building

      ========

      The ``build.py`` script automates the process of producing an

      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``.

      Next, invoke ``build.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
            
         $ python3.exe contrib\packaging\inno\build.py \

             --python c:\python27\python.exe

      .. 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.

      Additional options may be configured. Run ``build.py --help`` to

      see a list of program flags.

      MinGW

      =====

      It is theoretically possible to generate an installer that uses

      MinGW. This isn't well tested and ``build.py`` and may properly

      support it. See old versions of this file in version control for

      potentially useful hints as to how to achieve this.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages

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.
		* Python 3.5+ (to run the ``build.py`` script)

		Building
		========

		The ``build.py`` script automates the process of producing an
		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``.

		Next, invoke ``build.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
		$ python3.exe contrib\packaging\inno\build.py \
		--python c:\python27\python.exe

		.. 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.

		Additional options may be configured. Run ``build.py --help`` to
		see a list of program flags.

		MinGW
		=====

		It is theoretically possible to generate an installer that uses
		MinGW. This isn't well tested and ``build.py`` and may properly
		support it. See old versions of this file in version control for
		potentially useful hints as to how to achieve this.