jyapayne/swig
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

changes after running section number updater

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@9502 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2006-10-31 22:43:55 +00:00
commit 555e8f62d2
4 changed files with 20 additions and 25 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SWIG/Doc/Manual/Python.html
View file

@ -14,7 +14,6 @@
<li><a href="#Python_nn3">Preliminaries</a>
<ul>
<li><a href="#Python_nn4">Running SWIG</a>
<li><a href="#Python_nn5">Getting the right header files</a>
<li><a href="#Python_nn6">Compiling a dynamic module</a>
<li><a href="#Python_nn7">Using distutils</a>
<li><a href="#Python_nn8">Static linking</a>
@ -234,7 +233,7 @@ Type "copyright", "credits" or "license" for more information.
</pre>
</div>
<H3><a name="Python_nn6"></a>29.2.3 Compiling a dynamic module</H3>
<H3><a name="Python_nn6"></a>29.2.2 Compiling a dynamic module</H3>
<p>
@ -280,10 +279,10 @@ module actually consists of two files; <tt>socket.py</tt> and
<tt>_socket.so</tt>. Many other built-in Python modules follow a similar convention.
</p>
<H3><a name="Python_nn7"></a>29.2.4 Using distutils</H3>
<H3><a name="Python_nn7"></a>29.2.3 Using distutils</H3>
<H3><a name="Python_nn8"></a>29.2.5 Static linking</H3>
<H3><a name="Python_nn8"></a>29.2.4 Static linking</H3>
<p>
@ -362,7 +361,7 @@ If using static linking, you might want to rely on a different approach
(perhaps using distutils).
</p>
<H3><a name="Python_nn9"></a>29.2.6 Using your module</H3>
<H3><a name="Python_nn9"></a>29.2.5 Using your module</H3>
<p>
@ -519,7 +518,7 @@ system configuration (this requires root access and you will need to
read the man pages).
</p>
<H3><a name="Python_nn10"></a>29.2.7 Compilation of C++ extensions</H3>
<H3><a name="Python_nn10"></a>29.2.6 Compilation of C++ extensions</H3>
<p>
@ -616,7 +615,7 @@ erratic program behavior. If working with lots of software components, you
might want to investigate using a more formal standard such as COM.
</p>
<H3><a name="Python_nn11"></a>29.2.8 Compiling for 64-bit platforms</H3>
<H3><a name="Python_nn11"></a>29.2.7 Compiling for 64-bit platforms</H3>
<p>
@ -653,7 +652,7 @@ and -m64 allow you to choose the desired binary format for your python
extension.
</p>
<H3><a name="Python_nn12"></a>29.2.9 Building Python Extensions under Windows</H3>
<H3><a name="Python_nn12"></a>29.2.8 Building Python Extensions under Windows</H3>
<p>