cpython/Tools/msi
Martin v. Löwis 141f41ae1a Reuse componentids for *.dll across minor releases.
Indicate to the user when this is an upgrade installation.
Make CHM file non-advertised.
Backported to 2.4.
2005-03-15 00:39:40 +00:00
..
README.txt Move msi from sandbox to Tools. 2004-08-22 13:34:34 +00:00
msi.py Reuse componentids for *.dll across minor releases. 2005-03-15 00:39:40 +00:00
msilib.py Reuse componentids for *.dll across minor releases. 2005-03-15 00:39:40 +00:00
msisupport.c Avoid using *W functions on Win95. Backported to 2.4. 2005-02-18 16:18:09 +00:00
msisupport.mak Replace VB with VC. 2004-12-12 15:29:21 +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 SF bug #1061457: spelling error in win installer 2004-11-07 07:08:25 +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.