Fix a few minor markup nits.

This commit is contained in:
Fred Drake 2001-03-03 19:47:24 +00:00
parent f585bef504
commit 42119e49a9
1 changed files with 13 additions and 13 deletions

View File

@ -291,7 +291,7 @@ where \code{<plat>} expands to a brief description of the current
OS/hardware platform and Python version. The first form, with just a
\file{lib} directory, is used for ``pure module distributions''---that
is, module distributions that include only pure Python modules. If a
module distribution contains any extensions (modules written in C/C++),
module distribution contains any extensions (modules written in C/\Cpp),
then the second form, with two \code{<plat>} directories, is used. In
that case, the \file{temp.\filevar{plat}} directory holds temporary
files generated by the compile/link process that don't actually get
@ -434,15 +434,14 @@ build. Things to talk about:
\subsubsection{Borland C++}
This subsection describes the necessary steps to use Distutils with the
Borland C++ compiler version
5.5.\footnote{Check
Borland \Cpp{} compiler version 5.5.\footnote{Check
\url{http://www.borland.com/bcppbuilder/freecompiler/} for download}
%Should we mention that users have to create cfg-files for the compiler
%see also http://community.borland.com/article/0,1410,21205,00.html
First you have to know that the Borland's object file format(OMF) is
different from what is used by the Python version you can download
from the Python web site. (Python is built with Microsoft Visual C++,
from the Python web site. (Python is built with Microsoft Visual \Cpp,
which uses COFF as object file format.) For this reason you have to
convert Python's library \file{python20.lib} into the Borland format.
You can do this as follows:
@ -456,8 +455,8 @@ The \file{coff2omf} program comes with the Borland compiler. The file
installation. If your extension uses other libraries (zlib,...) you
have to convert them too.
The converted files have to reside in the same directories as the normal
libraries do.
The converted files have to reside in the same directories as the
normal libraries.
How does Distutils manage to use these libraries with their changed
names? If the extension needs a library (eg. \file{foo}) Distutils
@ -467,7 +466,7 @@ doesn't find such a special library it uses the default name
(\file{foo.lib}.)\footnote{This also means you could replace all
existing COFF-libraries with OMF-libraries of the same name.}
To let Distutils compile your extension with Borland C++ you now have
To let Distutils compile your extension with Borland \Cpp{} you now have
to type:
\begin{verbatim}
@ -484,17 +483,18 @@ file for Distutils (see section~\ref{config-files}.)
\subsubsection{GNU C / Cygwin / MinGW32}
This section describes the necessary steps to use Distutils with the
GNU C/C++ compilers in their Cygwin and MinGW32
distributions\footnote{Check
GNU C/\Cpp{} compilers in their Cygwin and MinGW32
distributions.\footnote{Check
\url{http://sources.redhat.com/cygwin/} and
\url{http://www.mingw.org} for more information}.
\url{http://www.mingw.org} for more information}
\XXX{For a Python which was built with Cygwin, all should work without
any of these following steps.}
For these compilers we have to create some special libraries too.
This task is more complex as for Borland's C++, because there is no
program to convert the library (inclusive the references on data structures.)
This task is more complex as for Borland's \Cpp, because there is no
program to convert the library (inclusive the references on data
structures.)
First you have to create a list of symbols which the Python DLL exports.
(You can find a good program for this task at