changes after maketoc.py was run

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6039 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-07-12 19:59:40 +00:00
commit 92aac0f28d
22 changed files with 436 additions and 362 deletions

View file

@ -12,28 +12,28 @@
<ul>
<li><a href="#n3">Windows Executable</a>
</ul>
<li><a href="#n5">SWIG Windows Examples</a>
<li><a href="#n4">SWIG Windows Examples</a>
<ul>
<li><a href="#n6">Instructions for using the Examples with Visual Studio</a>
<li><a href="#n5">Instructions for using the Examples with Visual Studio</a>
<ul>
<li><a href="#n7">Python</a>
<li><a href="#n8">TCL</a>
<li><a href="#n9">Perl</a>
<li><a href="#n10">Java</a>
<li><a href="#n11">Ruby</a>
<li><a href="#n12">C#</a>
<li><a href="#n6">Python</a>
<li><a href="#n7">TCL</a>
<li><a href="#n8">Perl</a>
<li><a href="#n9">Java</a>
<li><a href="#n10">Ruby</a>
<li><a href="#n11">C#</a>
</ul>
<li><a href="#n13">Instructions for using the Examples with other compilers</a>
<li><a href="#n12">Instructions for using the Examples with other compilers</a>
</ul>
<li><a href="#n14">SWIG on Cygwin and MinGW</a>
<li><a href="#n13">SWIG on Cygwin and MinGW</a>
<ul>
<li><a href="#n15">Building swig.exe on Windows</a>
<li><a href="#n14">Building swig.exe on Windows</a>
<ul>
<li><a href="#n16">Building swig.exe using MinGW and MSYS</a>
<li><a href="#n17">Building swig.exe using Cygwin</a>
<li><a href="#n18">Building swig.exe alternatives</a>
<li><a href="#n15">Building swig.exe using MinGW and MSYS</a>
<li><a href="#n16">Building swig.exe using Cygwin</a>
<li><a href="#n17">Building swig.exe alternatives</a>
</ul>
<li><a href="#n19">Running the examples on Windows using Cygwin</a>
<li><a href="#n18">Running the examples on Windows using Cygwin</a>
</ul>
</ul>
<!-- INDEX -->
@ -63,7 +63,7 @@ If you want to build your own swig.exe have a look at <a href="#swig_exe">Buildi
<a name="examples"></a>
<a name="n5"></a><H2>2.2 SWIG Windows Examples</H2>
<a name="n4"></a><H2>2.2 SWIG Windows Examples</H2>
Using Microsoft Visual C++ is the most common approach to compiling and linking SWIG's output.
@ -77,7 +77,7 @@ Alternatively run the <a href="#examples_cygwin">examples using Cygwin</a>.
More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html).
<a name="n6"></a><H3>2.2.1 Instructions for using the Examples with Visual Studio</H3>
<a name="n5"></a><H3>2.2.1 Instructions for using the Examples with Visual Studio</H3>
Ensure the SWIG executable is as supplied in the SWIG root directory in order for the examples to work.
@ -92,7 +92,7 @@ They are usually set from the Control Panel and System properties, but this depe
If you don't want to use environment variables then change all occurences of the environment variables in the .dsp files with hard coded values.
If you are interested in how the project files are set up there is explanatory information in some of the language module's documentation.
<a name="n7"></a><H4>2.2.1.1 Python</H4>
<a name="n6"></a><H4>2.2.1.1 Python</H4>
<b><tt>PYTHON_INCLUDE</tt></b> : Set this to the directory that contains python.h<br>
@ -103,7 +103,7 @@ PYTHON_INCLUDE: d:\python21\include<br>
PYTHON_LIB: d:\python21\libs\python21.lib<br>
</tt>
<a name="n8"></a><H4>2.2.1.2 TCL</H4>
<a name="n7"></a><H4>2.2.1.2 TCL</H4>
<b><tt>TCL_INCLUDE</tt></b> : Set this to the directory containing tcl.h<br>
@ -114,7 +114,7 @@ TCL_INCLUDE: d:\tcl\include<br>
TCL_LIB: d:\tcl\lib\tcl83.lib<br>
</tt>
<a name="n9"></a><H4>2.2.1.3 Perl</H4>
<a name="n8"></a><H4>2.2.1.3 Perl</H4>
<b><tt>PERL5_INCLUDE</tt></b> : Set this to the directory containing perl.h<br>
@ -125,7 +125,7 @@ PERL5_INCLUDE: D:\nsPerl5.004_04\lib\CORE<br>
PERL5_LIB: D:\nsPerl5.004_04\lib\CORE\perl.lib<br>
</tt>
<a name="n10"></a><H4>2.2.1.4 Java</H4>
<a name="n9"></a><H4>2.2.1.4 Java</H4>
<b><tt>JAVA_INCLUDE</tt></b> : Set this to the directory containing jni.h<br>
@ -136,7 +136,7 @@ JAVA_INCLUDE: d:\jdk1.3\include<br>
JAVA_BIN: d:\jdk1.3\bin<br>
</tt>
<a name="n11"></a><H4>2.2.1.5 Ruby</H4>
<a name="n10"></a><H4>2.2.1.5 Ruby</H4>
<b><tt>RUBY_INCLUDE</tt></b> : Set this to the directory containing ruby.h<br>
@ -147,25 +147,25 @@ RUBY_INCLUDE: D:\ruby\lib\ruby\1.6\i586-mswin32<br>
RUBY_LIB: D:\ruby\lib\mswin32-ruby16.lib<br>
</tt>
<a name="n12"></a><H4>2.2.1.6 C#</H4>
<a name="n11"></a><H4>2.2.1.6 C#</H4>
The C# examples do not require any environment variables to be set as a C# project file is included.
Just open up the .sln solution file in Visual Studio .NET 2003 and do a Rebuild All from the Build menu.
The accompanying C# and C++ project file are automatically used by the solution file.
<a name="n13"></a><H3>2.2.2 Instructions for using the Examples with other compilers</H3>
<a name="n12"></a><H3>2.2.2 Instructions for using the Examples with other compilers</H3>
If you do not have access to Visual C++ you will have to set up project files / Makefiles for your chosen compiler. There is a section in each of the language modules detailing what needs setting up using Visual C++ which may be of some guidance. Alternatively you may want to use Cygwin as described in the following section.
<a name="n14"></a><H2>2.3 SWIG on Cygwin and MinGW</H2>
<a name="n13"></a><H2>2.3 SWIG on Cygwin and MinGW</H2>
SWIG can also be compiled and run using <a href="http://www.cygwin.com">Cygwin</a> or <a href=http://www.mingw.org>MinGW</a> which provides a Unix like front end to Windows and comes free with gcc, an ANSI C/C++ compiler. However, this is not a recommended approach as the prebuilt executable is supplied.
<a name="swig_exe"></a>
<a name="n15"></a><H3>2.3.1 Building swig.exe on Windows</H3>
<a name="n14"></a><H3>2.3.1 Building swig.exe on Windows</H3>
If you want to replicate the build of swig.exe that comes with the download, follow the MinGW instructions below.
@ -173,7 +173,7 @@ This is not necessary to use the supplied swig.exe.
This information is provided for those that want to modify the SWIG source code in a Windows environment.
Normally this is not needed, so most people will want to ignore this section.
<a name="n16"></a><H4>2.3.1.1 Building swig.exe using MinGW and MSYS</H4>
<a name="n15"></a><H4>2.3.1.1 Building swig.exe using MinGW and MSYS</H4>
<ul>
@ -182,7 +182,7 @@ Normally this is not needed, so most people will want to ignore this section.
</ul>
<a name="n17"></a><H4>2.3.1.2 Building swig.exe using Cygwin</H4>
<a name="n16"></a><H4>2.3.1.2 Building swig.exe using Cygwin</H4>
Note that SWIG can also be built using Cygwin.
@ -192,7 +192,7 @@ Note that the Cygwin environment will also allow one to regenerate the autotool
These files are generated using the <tt>autogen.sh</tt> script and will only need regenerating in circumstances such as changing the build system.
<p>
<a name="n18"></a><H4>2.3.1.3 Building swig.exe alternatives</H4>
<a name="n17"></a><H4>2.3.1.3 Building swig.exe alternatives</H4>
If you don't want to install Cygwin or MinGW, use a different compiler to build
@ -201,7 +201,7 @@ file in order to build swig.exe from the Visual C++ IDE.
<a name="examples_cygwin"></a>
<a name="n19"></a><H3>2.3.2 Running the examples on Windows using Cygwin</H3>
<a name="n18"></a><H3>2.3.2 Running the examples on Windows using Cygwin</H3>
The examples and test-suite work as successfully on Cygwin as on any other Unix operating system.