diff --git a/SWIG/Doc/Manual/Windows.html b/SWIG/Doc/Manual/Windows.html index 2db7d2f39..4efabdeb3 100644 --- a/SWIG/Doc/Manual/Windows.html +++ b/SWIG/Doc/Manual/Windows.html @@ -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:

2.1.1 Windows Executable

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 Building swig.exe on Windows. +If you want to build your own swig.exe have a look at Building swig.exe on Windows.

2.1.2 Runtime Libraries

@@ -69,7 +69,7 @@ The Advanced Topics chapter has further details on t

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 SWIG Windows Examples section. +Before starting Visual C++, set the environment variables for your target language as described in the SWIG Windows Examples section. Next start Visual C++ and load the project file for your target language. 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. @@ -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. +

2.2 SWIG Windows Examples

@@ -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). 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. -Alternatively run the examples using Cygwin.

+Alternatively run the examples using Cygwin.

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 Cygwin or MinGW 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. +

2.3.1 Building swig.exe on Windows

@@ -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. +

2.3.2 Running the examples on Windows using Cygwin

@@ -218,4 +221,4 @@ Follow the Unix instructions in the README file in the SWIG root directory to bu

- \ No newline at end of file +