Update with links with names that don't get changed during TOC generation.

git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@4907 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2003-06-16 22:26:31 +00:00
commit 35f3bd7194

View file

@ -51,14 +51,14 @@ Usage within the Unix like environments MinGW and Cygwin is also detailed.
SWIG does not come with the usual Windows type installation program, however it is quite easy to get started. The main steps are: SWIG does not come with the usual Windows type installation program, however it is quite easy to get started. The main steps are:
<ul> <ul>
<li>Download the swigwin zip package from the <a href="http://www.swig.org">SWIG website</a> and unzip into a directory. This is all that needs downloading for the Windows platform. <li>Download the swigwin zip package from the <a href="http://www.swig.org">SWIG website</a> and unzip into a directory. This is all that needs downloading for the Windows platform.
<li>Set environment variables as described in the <a href="#n5">SWIG Windows Examples</a> section in order to run examples using Visual C++. <li>Set environment variables as described in the <a href="#examples">SWIG Windows Examples</a> section in order to run examples using Visual C++.
</ul> </ul>
<a name="n3"></a><H3>2.1.1 Windows Executable</H3> <a name="n3"></a><H3>2.1.1 Windows Executable</H3>
The swigwin distribution contains the SWIG Windows executable, swig.exe, which will run on 32 bit versions of Windows, ie Windows 95/98/ME/NT/2000/XP. The swigwin distribution contains the SWIG Windows executable, swig.exe, which will run on 32 bit versions of Windows, ie Windows 95/98/ME/NT/2000/XP.
If you want to build your own swig.exe have a look at <a href="#n14">Building swig.exe on Windows</a>. If you want to build your own swig.exe have a look at <a href="#swig_exe">Building swig.exe on Windows</a>.
<p> <p>
<a name="n4"></a><H3>2.1.2 Runtime Libraries</H3> <a name="n4"></a><H3>2.1.2 Runtime Libraries</H3>
@ -69,7 +69,7 @@ The <a href="Advanced.html">Advanced Topics</a> chapter has further details on t
<p> <p>
The runtime libraries which can be built have a Visual C++ project file (.dsp) file in the top level Runtime directory. The runtime libraries which can be built have a Visual C++ project file (.dsp) file in the top level Runtime directory.
Before starting Visual C++, set the environment variables for your target language as described in the <a href="#n5">SWIG Windows Examples</a> section. Before starting Visual C++, set the environment variables for your target language as described in the <a href="#examples">SWIG Windows Examples</a> section.
Next start Visual C++ and load the project file for your target language. Next start Visual C++ and load the project file for your target language.
Visual Studio will create a workspace file for you. Visual Studio will create a workspace file for you.
Ensure the Release build is selected then do a Rebuild All from the Build menu; the required environment variables are displayed with their current values. Ensure the Release build is selected then do a Rebuild All from the Build menu; the required environment variables are displayed with their current values.
@ -83,6 +83,7 @@ Ensure the dll is in the Windows path when executing your program requiring the
Note that the runtime libraries can also be built on Cygwin and is automatically done as part of the general build process on Cygwin. Note that the runtime libraries can also be built on Cygwin and is automatically done as part of the general build process on Cygwin.
<a name="examples"></a>
<a name="n5"></a><H2>2.2 SWIG Windows Examples</H2> <a name="n5"></a><H2>2.2 SWIG Windows Examples</H2>
@ -90,7 +91,7 @@ Using Microsoft Visual C++ is the most common approach to compiling and linking
The Examples directory has a few Visual C++ project files (.dsp files). The Examples directory has a few Visual C++ project files (.dsp files).
These were produced by Visual C++ 6, although they should also work in Visual C++ 5. These were produced by Visual C++ 6, although they should also work in Visual C++ 5.
These project files have been set up to execute SWIG in a custom build rule for the SWIG interface (.i) file. These project files have been set up to execute SWIG in a custom build rule for the SWIG interface (.i) file.
Alternatively run the <a href="#n18">examples using Cygwin</a>.<p> Alternatively run the <a href="#examples_cygwin">examples using Cygwin</a>.<p>
More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html). More information on each of the examples is available with the examples distributed with SWIG (Examples/index.html).
@ -172,6 +173,7 @@ If you do not have access to Visual C++ you will have to set up project files /
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. 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="n14"></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>
@ -208,6 +210,7 @@ SWIG. For example, all the source code files can be added to a Visual C++ projec
file in order to build swig.exe from the Visual C++ IDE. file in order to build swig.exe from the Visual C++ IDE.
<a name="examples_cygwin"></a>
<a name="n18"></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>