If you are using Python up to version 2.5.4, copy mfc71.dll into the dist directory that just got created. Which would allow you to skip the first build step and just run: python setup.py py2exe -b 1Ĭopy add_path.exe into the dist directory that just got created. Note: the combined command "python setup.py build -c mingw32 py2exe -b 1" that had been suggested in the past doesn't work correctly, as it doesn't include the extensions in the mercurial subdirectory and separate commands should be used as indicated.Īlternatively, you can create a file named setup.cfg in the root of the repository (C:\hg\hg-release) with the following contents: Open a command prompt window on C:\hg\hg-release, then build a standalone copy of the hg.exe program: python setup.py build -c mingw32 Once you have all this installed and built, clone a copy of the Mercurial repository you want to package, and name the repo C:\hg\hg-release. The pyOpenSSL package ( ) will enable SSL support in hg serve.
If you have pygments ( ) installed, this will allow use of the highlight extension. If you do this, then the bindings will be picked up and included in the installer, which means that the convert extension can work with Subversion repositories. It is extremely useful to have the Subversion Python bindings (see ) installed when building the installer. To build the html help files you need also:
#Install py2exe windows how to zip#
Visual C++ 2008 redistributable package (needed for Python 2.6)Īdd_path (you need only add_path.exe in the zip file)
#Install py2exe windows how to install#
Mfc71.dll (just download, don't install not needed for Python 2.6) It has the following prerequisites, at least as I build it: The standalone Windows installer for Mercurial is built in a somewhat jury-rigged fashion.
0 kommentar(er)
