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

Put the chapters back in order after erroneously incorrectly reordering them in last checkin

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@10294 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2008-03-02 22:41:58 +00:00
commit c99fe90574
35 changed files with 1572 additions and 1571 deletions
Download patch file Download diff file Expand all files Collapse all files

40
Doc/Manual/Windows.html
View file

@ -6,7 +6,7 @@
</head>
<body bgcolor="#ffffff">
<H1><a name="Windows"></a>34 Getting started on Windows </H1>
<H1><a name="Windows"></a>3 Getting started on Windows </H1>
<!-- INDEX -->
<div class="sectiontoc">
<ul>
@ -52,7 +52,7 @@ Usage within the Unix like environments MinGW and Cygwin is also detailed.
</p>
<H2><a name="Windows_installation"></a>34.1 Installation on Windows</H2>
<H2><a name="Windows_installation"></a>3.1 Installation on Windows</H2>
<p>
@ -63,7 +63,7 @@ SWIG does not come with the usual Windows type installation program, however it
<li>Set environment variables as described in the <a href="#Windows_examples">SWIG Windows Examples</a> section in order to run examples using Visual C++.
</ul>
<H3><a name="Windows_executable"></a>34.1.1 Windows Executable</H3>
<H3><a name="Windows_executable"></a>3.1.1 Windows Executable</H3>
<p>
@ -72,7 +72,7 @@ If you want to build your own swig.exe have a look at <a href="#Windows_swig_exe
</p>
<H2><a name="Windows_examples"></a>34.2 SWIG Windows Examples</H2>
<H2><a name="Windows_examples"></a>3.2 SWIG Windows Examples</H2>
<p>
@ -87,7 +87,7 @@ Alternatively run the <a href="#Windows_examples_cygwin">examples using Cygwin</
<p>
More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html).
<H3><a name="Windows_visual_studio"></a>34.2.1 Instructions for using the Examples with Visual Studio</H3>
<H3><a name="Windows_visual_studio"></a>3.2.1 Instructions for using the Examples with Visual Studio</H3>
<p>
@ -105,7 +105,7 @@ If you don't want to use environment variables then change all occurrences of th
If you are interested in how the project files are set up there is explanatory information in some of the language module's documentation.
</p>
<H4><a name="Windows_csharp"></a>34.2.1.1 C#</H4>
<H4><a name="Windows_csharp"></a>3.2.1.1 C#</H4>
<p>
@ -115,7 +115,7 @@ The accompanying C# and C++ project files are automatically used by the solution
</p>
<H4><a name="Windows_java"></a>34.2.1.2 Java</H4>
<H4><a name="Windows_java"></a>3.2.1.2 Java</H4>
<p>
@ -129,7 +129,7 @@ JAVA_BIN: D:\jdk1.3\bin<br>
</p>
<H4><a name="Windows_perl"></a>34.2.1.3 Perl</H4>
<H4><a name="Windows_perl"></a>3.2.1.3 Perl</H4>
<p>
@ -143,7 +143,7 @@ PERL5_LIB: D:\nsPerl5.004_04\lib\CORE\perl.lib<br>
</p>
<H4><a name="Windows_python"></a>34.2.1.4 Python</H4>
<H4><a name="Windows_python"></a>3.2.1.4 Python</H4>
<p>
@ -157,7 +157,7 @@ PYTHON_LIB: D:\python21\libs\python21.lib<br>
</p>
<H4><a name="Windows_tcl"></a>34.2.1.5 TCL</H4>
<H4><a name="Windows_tcl"></a>3.2.1.5 TCL</H4>
<p>
@ -171,7 +171,7 @@ TCL_LIB: D:\tcl\lib\tcl83.lib<br>
</p>
<H4><a name="Windows_r"></a>34.2.1.6 R</H4>
<H4><a name="Windows_r"></a>3.2.1.6 R</H4>
<p>
@ -185,7 +185,7 @@ R_LIB: C:\Program Files\R\R-2.5.1\bin\Rdll.lib<br>
</p>
<H4><a name="Windows_ruby"></a>34.2.1.7 Ruby</H4>
<H4><a name="Windows_ruby"></a>3.2.1.7 Ruby</H4>
<p>
@ -199,21 +199,21 @@ RUBY_LIB: D:\ruby\lib\mswin32-ruby16.lib<br>
</p>
<H3><a name="Windows_other_compilers"></a>34.2.2 Instructions for using the Examples with other compilers</H3>
<H3><a name="Windows_other_compilers"></a>3.2.2 Instructions for using the Examples with other compilers</H3>
<p>
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.
</p>
<H2><a name="Windows_cygwin_mingw"></a>34.3 SWIG on Cygwin and MinGW</H2>
<H2><a name="Windows_cygwin_mingw"></a>3.3 SWIG on Cygwin and MinGW</H2>
<p>
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.
</p>
<H3><a name="Windows_swig_exe"></a>34.3.1 Building swig.exe on Windows</H3>
<H3><a name="Windows_swig_exe"></a>3.3.1 Building swig.exe on Windows</H3>
<p>
@ -223,7 +223,7 @@ This information is provided for those that want to modify the SWIG source code
Normally this is not needed, so most people will want to ignore this section.
</p>
<H4><a name="Windows_mingw_msys"></a>34.3.1.1 Building swig.exe using MinGW and MSYS</H4>
<H4><a name="Windows_mingw_msys"></a>3.3.1.1 Building swig.exe using MinGW and MSYS</H4>
<p>
@ -325,7 +325,7 @@ make
</ol>
<H4><a name="Windows_cygwin"></a>34.3.1.2 Building swig.exe using Cygwin</H4>
<H4><a name="Windows_cygwin"></a>3.3.1.2 Building swig.exe using Cygwin</H4>
<p>
@ -336,7 +336,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>
<H4><a name="Windows_building_alternatives"></a>34.3.1.3 Building swig.exe alternatives</H4>
<H4><a name="Windows_building_alternatives"></a>3.3.1.3 Building swig.exe alternatives</H4>
<p>
@ -346,7 +346,7 @@ file in order to build swig.exe from the Visual C++ IDE.
</p>
<H3><a name="Windows_examples_cygwin"></a>34.3.2 Running the examples on Windows using Cygwin</H3>
<H3><a name="Windows_examples_cygwin"></a>3.3.2 Running the examples on Windows using Cygwin</H3>
<p>
@ -355,7 +355,7 @@ The modules which are known to work are Python, Tcl, Perl, Ruby, Java and C#.
Follow the Unix instructions in the README file in the SWIG root directory to build the examples.
</p>
<H2><a name="Windows_interface_file"></a>34.4 Microsoft extensions and other Windows quirks</H2>
<H2><a name="Windows_interface_file"></a>3.4 Microsoft extensions and other Windows quirks</H2>
<p>