cpython/Tools/msi
Serhiy Storchaka 9a118f1dc3 Issue #26778: Fixed "a/an/and" typos in code comment and documentation. 2016-04-17 09:37:36 +03: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 #26778: Fixed "a/an/and" typos in code comment and documentation. 2016-04-17 09:37:36 +03:00
msilib.py #22398 Tools/msi enhancements for 2.7 2014-09-12 11:48:13 -07: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 Generates installer product codes for future releases. 2015-06-03 08:58:14 -07: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.