cpython/Tools/msi
Terry Jan Reedy 6bf9b85859 Issue #17047: removed doubled words in Doc/*, Mac/*, and Tool/*
found by Serhiy Storchaka and Matthew Barnett
2013-03-11 17:09:58 -04:00
..
README.txt Move msi from sandbox to Tools. 2004-08-22 13:34:34 +00:00
crtlicense.txt #4700: crtlicense.txt is displayed by the license() command and should be kept ascii-only. 2008-12-19 22:56:48 +00:00
msi.py Issue #6807: Run msisupport.mak earlier. 2012-02-21 18:12:02 +01:00
msilib.py Issue #17047: removed doubled words in Doc/*, Mac/*, and Tool/* 2013-03-11 17:09:58 -04:00
msisupport.c Untabify C files. Will watch buildbots. 2010-05-09 14:46:46 +00:00
msisupport.mak Port to VS 2008. Drop W9x support. 2008-05-09 20:11:37 +00:00
schema.py Extend sizes of various fields, to support the CRT90 merge module. 2008-04-05 15:45:25 +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 Add 2.7.3rc2 uuid 2012-03-18 23:46:56 +01: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.