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

Update with regard runtime library

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@6058 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2004-07-23 22:08:48 +00:00
commit fb6cac8590
1 changed files with 8 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

15
SWIG/Doc/Manual/Advanced.html
View file

@ -59,7 +59,7 @@ Consider for a moment the following two interface files :<p>
class a { class a {
public: public:
a(); a();
~a(); virtual ~a();
void foo(double); void foo(double);
}; };
@ -141,11 +141,11 @@ void *__embedfunc(void *);
</pre></blockquote> </pre></blockquote>
<p> <p>
Now, run SWIG and compile as follows:<p> Now, assuming you have built the <a href="Modules.html">runtime library</a> as <tt>swigruntcl</tt>, run SWIG and compile as follows:<p>
<p> <p>
<blockquote><pre> <blockquote><pre>
% <b>swig -c -tcl mytclsh.i</b> % <b>swig -c -tcl mytclsh.i</b>
% <b>gcc mytclsh_wrap.c -I/usr/local/include -L/usr/local/lib -ltcl -lswigtcl8 -ldl -lm \ % <b>gcc mytclsh_wrap.c -I/usr/local/include -L/usr/local/lib -ltcl -lswigruntcl -ldl -lm \
-o tclsh</b> -o tclsh</b>
</pre></blockquote> </pre></blockquote>
This produces a new executable "<tt>tclsh</tt>" that contains a copy of the SWIG runtime library. The weird <tt>__embedfunc()</tt> function is needed to force the functions in the runtime library to be included in the final executable.<p> This produces a new executable "<tt>tclsh</tt>" that contains a copy of the SWIG runtime library. The weird <tt>__embedfunc()</tt> function is needed to force the functions in the runtime library to be included in the final executable.<p>
@ -157,7 +157,7 @@ To make new dynamically loadable SWIG modules, simply compile as follows :<p>
% <b>gcc -c example_wrap.c -I/usr/local/include</b> % <b>gcc -c example_wrap.c -I/usr/local/include</b>
% <b>ld -shared example_wrap.o -o example.so</b> % <b>ld -shared example_wrap.o -o example.so</b>
</pre></blockquote> </pre></blockquote>
Linking against the <tt>swigtcl8</tt> library is no longer necessary as all of the functions are now included in the <tt>tclsh</tt> executable and will be resolved when your module is loaded. Linking against the <tt>swigruntcl</tt> library is no longer necessary as all of the functions are now included in the <tt>tclsh</tt> executable and will be resolved when your module is loaded.
However, some operating systems, like Windows, will still require linking with the libraries so that there are no unresolved symbols.<p> However, some operating systems, like Windows, will still require linking with the libraries so that there are no unresolved symbols.<p>
<p> <p>
2. Using shared library versions of the runtime library<p> 2. Using shared library versions of the runtime library<p>
@ -168,7 +168,8 @@ If supported on your machine, the runtime libraries will be built as shared libr
% <b>ld -shared example_wrap.o -o libexample.so</b> # Irix % <b>ld -shared example_wrap.o -o libexample.so</b> # Irix
% <b>gcc -shared example_wrap.o -o libexample.so</b> # Linux % <b>gcc -shared example_wrap.o -o libexample.so</b> # Linux
% <b>ld -G example_wrap.o -o libexample.so</b> # Solaris % <b>ld -G example_wrap.o -o libexample.so</b> # Solaris
&gt; <b>cl /LD example_wrap.obj /o example.dll swigtcl8.lib tcl83.lib /link /LIBPATH:c:\SWIG\Runtime /LIBPATH:c:\Tcl\lib</b> # Windows VC++ &gt; <b>cl /LD example_wrap.obj /o example.dll swigruntcl.lib tcl83.lib
/link /LIBPATH:PathToRuntimeLibrary /LIBPATH:c:\Tcl\lib</b> # Windows VC++
</pre></blockquote> </pre></blockquote>
In order for the <tt>libexample.so</tt> library to work, it needs to be placed in a location where the dynamic loader can find it. In order for the <tt>libexample.so</tt> library to work, it needs to be placed in a location where the dynamic loader can find it.
@ -183,10 +184,10 @@ If the shared library file is not in any of these directories, it results in an
On most machines, you can change the loader search path by changing the path (Windows) or environment variable <tt>LD_LIBRARY_PATH</tt> (Unix), e.g.<p> On most machines, you can change the loader search path by changing the path (Windows) or environment variable <tt>LD_LIBRARY_PATH</tt> (Unix), e.g.<p>
<p> <p>
<blockquote><pre>% <b>setenv LD_LIBRARY_PATH .:/home/beazley/packages/lib</b></pre></blockquote> <blockquote><pre>% <b>setenv LD_LIBRARY_PATH .:/home/beazley/packages/lib</b></pre></blockquote>
A somewhat better approach is to link your module with the proper path encoded. This is typically done using the `<tt>-rpath</tt>' or `<tt>-R</tt>' option to your linker (see the man page). For example:<p> A somewhat better approach is to link your module with the proper path encoded. This is typically done using the `<tt>-rpath</tt>' or `<tt>-R</tt>' option to your linker on Unix (see the man page). For example:<p>
<p> <p>
<blockquote><pre>% <b>ld -shared example_wrap.o example.o -rpath /home/beazley/packages/lib \ <blockquote><pre>% <b>ld -shared example_wrap.o example.o -rpath /home/beazley/packages/lib \
-L/home/beazley/packages/lib -lswigtcl8.so -o example.so</b> -L/home/beazley/packages/lib -lswigruntcl.so -o example.so</b>
</pre></blockquote> </pre></blockquote>
The <tt>-rpath</tt> option encodes the location of shared libraries into your modules and gets around having to set the <tt>LD_LIBRARY_PATH</tt> variable.<p> The <tt>-rpath</tt> option encodes the location of shared libraries into your modules and gets around having to set the <tt>LD_LIBRARY_PATH</tt> variable.<p>
<p> <p>