mirrors/cpython
1
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2025-10-31 10:26:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

Minor markup nits.

Browse source
This commit is contained in:
Fred Drake 1998-04-02 16:19:15 +00:00
parent f14e2f8a04
commit b789c70d05
2 changed files with 24 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

22
Doc/ext.tex
View file

@ -1309,9 +1309,11 @@ otherwise you have to select it as a build option (see below). Once
configured, dynamic loading is trivial to use: when a Python program configured, dynamic loading is trivial to use: when a Python program
executes \code{import spam}, the search for modules tries to find a executes \code{import spam}, the search for modules tries to find a
file \file{spammodule.o} (\file{spammodule.so} when using shared file \file{spammodule.o} (\file{spammodule.so} when using shared
libraries) in the module search path, and if one is found, it is libraries) in the module search path,%
loaded into the executing binary and executed. Once loaded, the \indexiii{module}{search}{path}
module acts just like a built-in extension module. and if one is found, it is loaded into the executing binary and
executed. Once loaded, the module acts just like a built-in extension
module.
The advantages of dynamic loading are twofold: the ``core'' Python The advantages of dynamic loading are twofold: the ``core'' Python
binary gets smaller, and users can extend Python with their own binary gets smaller, and users can extend Python with their own
@ -1411,10 +1413,10 @@ described earlier).
Note that in all cases you will have to create your own Makefile that Note that in all cases you will have to create your own Makefile that
compiles your module file(s). This Makefile will have to pass two compiles your module file(s). This Makefile will have to pass two
\samp{-I} arguments to the \C{} compiler which will make it find the \samp{-I} arguments to the \C{} compiler which will make it find the
Python header files. If the Make variable \var{PYTHONTOP} points to Python header files. If the Make variable \makevar{PYTHONTOP} points to
the toplevel Python directory, your \var{CFLAGS} Make variable should the toplevel Python directory, your \makevar{CFLAGS} Make variable should
contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}. contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}.
(Most header files are in the \file{Include} subdirectory, but the (Most header files are in the \file{Include/} subdirectory, but the
\file{config.h} header lives in the toplevel directory.) \file{config.h} header lives in the toplevel directory.)
@ -1461,7 +1463,8 @@ additional \C{} flag \samp{-G0} (or \samp{-G 0}). This instructs the
assembler to generate position-independent code. assembler to generate position-independent code.
You don't need to link the resulting \file{spammodule.o} file; just You don't need to link the resulting \file{spammodule.o} file; just
copy it into a directory along the Python module search path. copy it into a directory along the Python module search path.%
\indexiii{module}{search}{path}
The first time your extension is loaded, it takes some extra time and The first time your extension is loaded, it takes some extra time and
a few messages may be printed. This creates a file a few messages may be printed. This creates a file
@ -1486,7 +1489,8 @@ normally only \samp{-l} options or absolute pathnames of libraries
\label{gnuLinking} \label{gnuLinking}
Just copy \file{spammodule.o} into a directory along the Python module Just copy \file{spammodule.o} into a directory along the Python module
search path. search path.%
\indexiii{module}{search}{path}
If your extension modules uses additional system libraries, you must If your extension modules uses additional system libraries, you must
create a file \file{spammodule.libs} in the same directory as the create a file \file{spammodule.libs} in the same directory as the
@ -1495,6 +1499,4 @@ whitespace-separated absolute pathnames of libraries (\samp{.a}
files). No \samp{-l} options can be used. files). No \samp{-l} options can be used.
\input{ext.ind}
\end{document} \end{document}

22
Doc/ext/ext.tex
View file

@ -1309,9 +1309,11 @@ otherwise you have to select it as a build option (see below). Once
configured, dynamic loading is trivial to use: when a Python program configured, dynamic loading is trivial to use: when a Python program
executes \code{import spam}, the search for modules tries to find a executes \code{import spam}, the search for modules tries to find a
file \file{spammodule.o} (\file{spammodule.so} when using shared file \file{spammodule.o} (\file{spammodule.so} when using shared
libraries) in the module search path, and if one is found, it is libraries) in the module search path,%
loaded into the executing binary and executed. Once loaded, the \indexiii{module}{search}{path}
module acts just like a built-in extension module. and if one is found, it is loaded into the executing binary and
executed. Once loaded, the module acts just like a built-in extension
module.
The advantages of dynamic loading are twofold: the ``core'' Python The advantages of dynamic loading are twofold: the ``core'' Python
binary gets smaller, and users can extend Python with their own binary gets smaller, and users can extend Python with their own
@ -1411,10 +1413,10 @@ described earlier).
Note that in all cases you will have to create your own Makefile that Note that in all cases you will have to create your own Makefile that
compiles your module file(s). This Makefile will have to pass two compiles your module file(s). This Makefile will have to pass two
\samp{-I} arguments to the \C{} compiler which will make it find the \samp{-I} arguments to the \C{} compiler which will make it find the
Python header files. If the Make variable \var{PYTHONTOP} points to Python header files. If the Make variable \makevar{PYTHONTOP} points to
the toplevel Python directory, your \var{CFLAGS} Make variable should the toplevel Python directory, your \makevar{CFLAGS} Make variable should
contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}. contain the options \samp{-I\$(PYTHONTOP) -I\$(PYTHONTOP)/Include}.
(Most header files are in the \file{Include} subdirectory, but the (Most header files are in the \file{Include/} subdirectory, but the
\file{config.h} header lives in the toplevel directory.) \file{config.h} header lives in the toplevel directory.)
@ -1461,7 +1463,8 @@ additional \C{} flag \samp{-G0} (or \samp{-G 0}). This instructs the
assembler to generate position-independent code. assembler to generate position-independent code.
You don't need to link the resulting \file{spammodule.o} file; just You don't need to link the resulting \file{spammodule.o} file; just
copy it into a directory along the Python module search path. copy it into a directory along the Python module search path.%
\indexiii{module}{search}{path}
The first time your extension is loaded, it takes some extra time and The first time your extension is loaded, it takes some extra time and
a few messages may be printed. This creates a file a few messages may be printed. This creates a file
@ -1486,7 +1489,8 @@ normally only \samp{-l} options or absolute pathnames of libraries
\label{gnuLinking} \label{gnuLinking}
Just copy \file{spammodule.o} into a directory along the Python module Just copy \file{spammodule.o} into a directory along the Python module
search path. search path.%
\indexiii{module}{search}{path}
If your extension modules uses additional system libraries, you must If your extension modules uses additional system libraries, you must
create a file \file{spammodule.libs} in the same directory as the create a file \file{spammodule.libs} in the same directory as the
@ -1495,6 +1499,4 @@ whitespace-separated absolute pathnames of libraries (\samp{.a}
files). No \samp{-l} options can be used. files). No \samp{-l} options can be used.
\input{ext.ind}
\end{document} \end{document}