[Python-checkins] python/dist/src/Doc/ext windows.tex,1.3.6.1,1.3.6.2
fdrake@sourceforge.net
fdrake@sourceforge.net
Thu, 18 Apr 2002 21:06:08 -0700
Update of /cvsroot/python/python/dist/src/Doc/ext
In directory usw-pr-cvs1:/tmp/cvs-serv19851/ext
Modified Files:
Tag: release22-maint
windows.tex
Log Message:
Clean up the use of version numbers in filenames; always use an "abstract"
version number, and explain what it is at the top of the chapter.
This closes SF bug #225003.
Index: windows.tex
===================================================================
RCS file: /cvsroot/python/python/dist/src/Doc/ext/windows.tex,v
retrieving revision 1.3.6.1
retrieving revision 1.3.6.2
diff -C2 -d -r1.3.6.1 -r1.3.6.2
*** windows.tex 15 Mar 2002 10:29:08 -0000 1.3.6.1
--- windows.tex 19 Apr 2002 04:06:06 -0000 1.3.6.2
***************
*** 15,18 ****
--- 15,29 ----
Python; typically Microsoft Visual \Cpp.
+ \begin{notice}
+ This chapter mentions a number of filenames that include an encoded
+ Python version number. These filenames are represented with the
+ version number shown as \samp{XY}; in practive, \character{X} will
+ be the major version number and \character{Y} will be the minor
+ version number of the Python release you're working with. For
+ example, if you are using Python 2.2.1, \samp{XY} will actually be
+ \samp{22}.
+ \end{notice}
+
+
\section{A Cookbook Approach \label{win-cookbook}}
***************
*** 168,176 ****
Select ``Win32 Release'' in the ``Settings for'' dropdown list.
Click the Link tab, choose the Input Category, and append
! \code{python22.lib} to the list in the ``Object/library modules''
box.
Select ``Win32 Debug'' in the ``Settings for'' dropdown list, and
! append \code{python22_d.lib} to the list in the ``Object/library
modules'' box. Then click the C/\Cpp{} tab, select ``Code
Generation'' from the Category dropdown list, and select ``Debug
--- 179,187 ----
Select ``Win32 Release'' in the ``Settings for'' dropdown list.
Click the Link tab, choose the Input Category, and append
! \code{pythonXY.lib} to the list in the ``Object/library modules''
box.
Select ``Win32 Debug'' in the ``Settings for'' dropdown list, and
! append \code{pythonXY_d.lib} to the list in the ``Object/library
modules'' box. Then click the C/\Cpp{} tab, select ``Code
Generation'' from the Category dropdown list, and select ``Debug
***************
*** 276,286 ****
this section is MSV\Cpp{} specific.
! When creating DLLs in Windows, you must pass \file{python15.lib} to
the linker. To build two DLLs, spam and ni (which uses C functions
found in spam), you could use these commands:
\begin{verbatim}
! cl /LD /I/python/include spam.c ../libs/python15.lib
! cl /LD /I/python/include ni.c spam.lib ../libs/python15.lib
\end{verbatim}
--- 287,297 ----
this section is MSV\Cpp{} specific.
! When creating DLLs in Windows, you must pass \file{pythonXY.lib} to
the linker. To build two DLLs, spam and ni (which uses C functions
found in spam), you could use these commands:
\begin{verbatim}
! cl /LD /I/python/include spam.c ../libs/pythonXY.lib
! cl /LD /I/python/include ni.c spam.lib ../libs/pythonXY.lib
\end{verbatim}
***************
*** 288,292 ****
\file{spam.dll} and \file{spam.lib}. \file{Spam.dll} does not contain
any Python functions (such as \cfunction{PyArg_ParseTuple()}), but it
! does know how to find the Python code thanks to \file{python15.lib}.
The second command created \file{ni.dll} (and \file{.obj} and
--- 299,303 ----
\file{spam.dll} and \file{spam.lib}. \file{Spam.dll} does not contain
any Python functions (such as \cfunction{PyArg_ParseTuple()}), but it
! does know how to find the Python code thanks to \file{pythonXY.lib}.
The second command created \file{ni.dll} (and \file{.obj} and