Document the available command line flags for bdist_wininst, which are

avaliable in the Python 2.2 branch.

I've left out some flags which are more thought for debugging, if
someone needs them, he can always look at the output of --help.

I'm sure Fred will make some adjustments, so I'll only mark this as a
2.2 bugfix candidate.

There are more options available in the current CVS bdist_wininst,
I will document them after this is in.

diff --git a/Doc/dist/dist.tex b/Doc/dist/dist.tex
index 22d60e45b751f75bd094962e752b1ad93b4ec243..ecac8f82ef39ce0debe40dff03827bd45db30442 100644 (file)
--- a/Doc/dist/dist.tex
+++ b/Doc/dist/dist.tex
@@ -1265,14 +1265,14 @@ extending the Distutils.)
 \subsection{Creating Windows Installers}
 \label{creating-wininst}
 
-Executable installers are the natural format for binary
-distributions on Windows.  They display a nice graphical user interface,
-display some information about the module distribution to be installed taken
+Executable installers are the natural format for binary distributions
+on Windows.  They display a nice graphical user interface, display
+some information about the module distribution to be installed taken
 from the metadata in the setup script, let the user select a few
-(currently maybe too few) options, and start or cancel the installation.
+options, and start or cancel the installation.
 
-Since the metadata is taken from the setup script, creating
-Windows installers is usually as easy as running:
+Since the metadata is taken from the setup script, creating Windows
+installers is usually as easy as running:
 
 \begin{verbatim}
 python setup.py bdist_wininst
@@ -1284,22 +1284,36 @@ or the \command{bdist} command with the \longprogramopt{formats} option:
 python setup.py bdist --formats=wininst
 \end{verbatim}
 
-If you have a pure module distribution (only containing pure
-Python modules and packages), the resulting installer will be
-version independent and have a name like \file{foo-1.0.win32.exe}.
-These installers can even be created on \UNIX{} or MacOS platforms.
+If you have a pure module distribution (only containing pure Python
+modules and packages), the resulting installer will be version
+independent and have a name like \file{foo-1.0.win32.exe}.  These
+installers can even be created on \UNIX{} or MacOS platforms.
 
 If you have a non-pure distribution, the extensions can only be
 created on a Windows platform, and will be Python version dependent.
 The installer filename will reflect this and now has the form
-\file{foo-1.0.win32-py2.0.exe}. You have to create a separate installer
+\file{foo-1.0.win32-py2.0.exe}.  You have to create a separate installer
 for every Python version you want to support.
 
 The installer will try to compile pure modules into bytecode after
-installation on the target system in normal and optimizing mode.
-If you don't want this to happen for some reason, you can run
-the bdist_wininst command with the \longprogramopt{no-target-compile} and/or
-the \longprogramopt{no-target-optimize} option.
+installation on the target system in normal and optimizing mode.  If
+you don't want this to happen for some reason, you can run the
+bdist_wininst command with the \longprogramopt{no-target-compile}
+and/or the \longprogramopt{no-target-optimize} option.
+
+By default the installer will display the cool Python powered logo
+when it is run, but you can also supply your own bitmap which must be
+a Windows .bmp file with the \longprogramopt{bitmap} option.
+
+The installer will also display a large title on the desktop
+background window when it is run, which is constructed from the name
+of your distribution and the version number.  This can be changed to
+another text by using the \longprogramopt{title} option.
+
+The installer file will be written to the ``distribution directory''
+--- normally \file{dist/}, but customizable with the
+\longprogramopt{dist-dir} option.
+
 
 \section{Examples}
 \label{examples}