Improved support for native Windows compilers.
It is no longer necessary to explicitly export the SWIG_init DLL function by passing flags to the linker. git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk/SWIG@4340 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
parent
41d8ef047a
commit
55d3b5dcca
4 changed files with 6 additions and 10 deletions
|
|
@ -317,10 +317,6 @@ of your Ruby module (i.e.. example.dll). Next add the Ruby library file to your
|
|||
link libraries under Object/Library modules. For example "mswin32-ruby16.lib.
|
||||
You also need to add the path to the library under the Input tab - Additional
|
||||
library path.
|
||||
<li>Finally still under the Link tab, add the dll entry point in the Project
|
||||
Options: Use "/EXPORT:Init_example" for when you have set the swig module name
|
||||
to 'example'. In general use "/EXPORT:Init_<module>", where <module> is the
|
||||
swig module name (specified using %module in your interface file).
|
||||
<li>Build your project.
|
||||
|
||||
</ul>
|
||||
|
|
@ -3007,4 +3003,4 @@ for more details).
|
|||
|
||||
<address>SWIG 1.3 - Last Modified : $Date$</address>
|
||||
</body>
|
||||
</html>
|
||||
</html>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue