cpython

History

Thomas Heller 3bd3315e49 Per Martins request, add empty.vbs to Tools\msi\msi.py. This file is used by test_startfile.py.		2006-04-04 18:41:13 +00:00
..
README.txt	Move msi from sandbox to Tools.	2004-08-22 13:34:34 +00:00
msi.py	Per Martins request, add empty.vbs to Tools\msi\msi.py.	2006-04-04 18:41:13 +00:00
msilib.py	Open dll file in binary.	2006-03-05 13:52:20 +00:00
msisupport.c	Avoid using *W functions on Win95. Backported to 2.4.	2005-02-18 16:18:09 +00:00
msisupport.mak	Add build support for AMD64.	2006-02-14 20:42:55 +00:00
schema.py	Whitespace normalization.	2004-08-22 19:42:56 +00:00
sequence.py	Move msi from sandbox to Tools.	2004-08-22 13:34:34 +00:00
uisample.py	fix typos, mostly in comments	2005-10-28 14:39:47 +00:00
uuids.py	Move product_codes in their own file.	2006-03-28 18:30:05 +00: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.