mirror of https://github.com/python/cpython.git
1c4c306626
svn+ssh://pythondev@svn.python.org/python/trunk ........ r66304 | martin.v.loewis | 2008-09-08 14:02:45 +0200 (Mo, 08 Sep 2008) | 2 lines Allow passing the MSI file name to merge.py. ........ r66305 | martin.v.loewis | 2008-09-08 15:50:10 +0200 (Mo, 08 Sep 2008) | 3 lines Issue #2271: Set SecureCustomProperties so that installation will properly use the TARGETDIR even for unprivileged users. ........ r66307 | martin.v.loewis | 2008-09-08 18:15:38 +0200 (Mo, 08 Sep 2008) | 1 line Add UUIDs for upcoming releases ........ |
||
|---|---|---|
| .. | ||
| README.txt | ||
| merge.py | ||
| msi.py | ||
| msilib.py | ||
| msisupport.c | ||
| msisupport.mak | ||
| schema.py | ||
| sequence.py | ||
| uisample.py | ||
| uuids.py | ||
README.txt
Packaging Python as a Microsoft Installer Package (MSI) ======================================================= Using this library, Python can be packaged as a MS-Windows MSI file. To generate an installer package, you need a build tree. By default, the build tree root directory is assumed to be in "../..". This location can be changed by adding a file config.py; see the beginning of msi.py for additional customization options. The packaging process assumes that binaries have been generated according to the instructions in PCBuild/README.txt, and that you have either Visual Studio or the Platform SDK installed. In addition, you need the Python COM extensions, either from PythonWin, or from ActivePython. To invoke the script, open a cmd.exe window which has cabarc.exe in its PATH (e.g. "Visual Studio .NET 2003 Command Prompt"). Then invoke <path-to-python.exe> msi.py If everything succeeds, pythonX.Y.Z.msi is generated in the current directory.