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

Updated documentation to reflect the -runtime and -noruntime commandline options for working with multiple modules / runtime library

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@6024 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-07-10 16:39:31 +00:00
commit 41e9a9c984
7 changed files with 52 additions and 108 deletions
Download patch file Download diff file Expand all files Collapse all files

27
Doc/Manual/Windows.html
View file

@ -11,7 +11,6 @@
<li><a href="#n2">Installation on Windows</a>
<ul>
<li><a href="#n3">Windows Executable</a>
<li><a href="#n4">Runtime Libraries</a>
</ul>
<li><a href="#n5">SWIG Windows Examples</a>
<ul>
@ -42,7 +41,7 @@
This chapter describes SWIG usage on Microsoft Windows.
Installing SWIG and running the examples is covered as well as building the SWIG executable and runtime libraries.
Installing SWIG and running the examples is covered as well as building the SWIG executable.
Usage within the Unix like environments MinGW and Cygwin is also detailed.
@ -62,27 +61,6 @@ The swigwin distribution contains the SWIG Windows executable, swig.exe, which w
If you want to build your own swig.exe have a look at <a href="#swig_exe">Building swig.exe on Windows</a>.
<p>
<a name="n4"></a><H3>2.1.2 Runtime Libraries</H3>
The vast majority of users do not use the SWIG runtime libraries so feel free to ignore this section.
The <a href="Advanced.html">Advanced Topics</a> chapter has further details on the runtime libraries.
<p>
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="#examples">SWIG Windows Examples</a> 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.
If all goes well the runtime library dll will appear in the Runtime directory.
<p>
Whenever using the runtime library, link against the <tt>.lib</tt> file which also is generated into this directory.
Ensure the dll is in the Windows path when executing your program requiring the dll.
<p>
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>
@ -210,7 +188,6 @@ Normally this is not needed, so most people will want to ignore this section.
Note that SWIG can also be built using Cygwin.
However, the SWIG will then require the Cygwin DLL when executing.
Follow the Unix instructions in the README file in the SWIG root directory.
The runtime libraries are also built as part of this build process.
Note that the Cygwin environment will also allow one to regenerate the autotool generated files which are supplied with the release distribution.
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>
@ -234,4 +211,4 @@ Follow the Unix instructions in the README file in the SWIG root directory to bu
<p>
</body>
</html>
</html>