cpython/Tools/msi
Steve Dower 3a43dbfabf Drop pydocgui.pyw from the distribution (post-merge merge from 165aa40bfe2e) 2014-10-08 08:36:16 -07:00
..
README.txt
crtlicense.txt Merged revisions 67859 via svnmerge from 2008-12-19 22:58:37 +00:00
msi.py Drop pydocgui.pyw from the distribution (post-merge merge from 165aa40bfe2e) 2014-10-08 08:36:16 -07:00
msilib.py #18803: fix more typos. Patch by Févry Thibault. 2013-08-26 01:32:56 +03:00
msisupport.c Recorded merge of revisions 81032 via svnmerge from 2010-05-09 16:14:21 +00:00
msisupport.mak Merged revisions 62954-62959,62961,62963-62967,62969-62970,62972-62973,62975-62976,62978-62982,62984,62987-62996 via svnmerge from 2008-05-15 22:51:26 +00:00
schema.py Fix a few typos and a double semicolon. Patch by Eitan Adler. 2013-01-27 06:20:14 +02:00
sequence.py Revert r63378. These files need to stay compatible with Python 2.x (until Python 3.0 is actually used to package Python). 2008-07-18 18:40:42 +00:00
uisample.py Fix a few typos and a double semicolon. Patch by Eitan Adler. 2013-01-27 06:20:14 +02:00

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.