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

Add note about new windows.i file

Browse source 
git-svn-id: https://swig.svn.sourceforge.net/svnroot/swig/trunk@8040 626c5289-ae23-0410-ae9c-e8d60b6d4f22
This commit is contained in:
William S Fulton 2005-12-22 23:25:25 +00:00
commit 505e528997
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
SWIG/Doc/Manual/Windows.html
View file

@ -37,6 +37,7 @@
</ul> </ul>
<li><a href="#examples_cygwin">Running the examples on Windows using Cygwin</a> <li><a href="#examples_cygwin">Running the examples on Windows using Cygwin</a>
</ul> </ul>
<li><a href="#Windows_interface_file">Microsoft extensions and other Windows quirks</a>
</ul> </ul>
</div> </div>
<!-- INDEX --> <!-- INDEX -->
@ -240,5 +241,23 @@ The modules which are known to work are Python, Tcl, Perl, Ruby, Java and C#.
Follow the Unix instructions in the README file in the SWIG root directory to build the examples. Follow the Unix instructions in the README file in the SWIG root directory to build the examples.
</p> </p>
<H2><a name="Windows_interface_file"></a>3.4 Microsoft extensions and other Windows quirks</H2>
<p>
A common problem when using SWIG on Windows are the Microsoft function calling conventions which are not in the C++ standard.
SWIG parses ISO C/C++ so cannot deal with proprietary conventions such as <tt>__declspec(dllimport)</tt>, <tt>__stdcall</tt> etc.
There is a Windows interface file, <tt>windows.i</tt>, to deal with these calling conventions though.
The file also contains typemaps for handling commonly used Windows specific types such as <tt>__int64</tt>, <tt>BOOL</tt>, <tt>DWORD</tt> etc.
Include it like you would any other interface file, for example:
<div class="code"><pre>
%include &lt;windows.i&gt;
__declspec(dllexport) ULONG __stdcall foo(DWORD, __int32);
</pre></div>
</p>
</body> </body>
</html> </html>