I writing a wrapper, would it be correct to more or less follow this guide, on winelib dll&#39;s? <a href="http://www.winehq.org/site/docs/winelib-guide/bindlls">http://www.winehq.org/site/docs/winelib-guide/bindlls</a><br>
<br>I&#39;ve never coded anything for Wine before so I want to make sure I do it right from the beginning instead of having to go back and make drastic changes.<br><br>I&#39;ll be looking at that opengl32 perl script because there is 102 pages of functions that cudart.dll and libcudart.so both contain.<br>
<br><br><div class="gmail_quote">On Sun, Jul 6, 2008 at 6:53 PM, Michael Karcher &lt;<a href="mailto:wine@mkarcher.dialup.fu-berlin.de">wine@mkarcher.dialup.fu-berlin.de</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is not going to work. PE style dynamic linking works quite<br>
different from ELF style dynamic linking. Wine can not link native ELF<br>
libraries to windows applications. The .dll.so files from wine are<br>
special in being ELF files but containing extra information that allows<br>
the Wine dynamic linker to link it into PE processes.<br>
<div class="Ih2E3d"></div></blockquote><div>&nbsp;</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>This is right. You need at least a correct .spec file to make a wine<br>
dll. You still have to implement a wrapper for each function, as Windows<br>
usually uses the stdcall calling convention, whereas linux uses cdecl by<br>
default. There might be some way to automate writing the wrapper<br>
functions.<br>
<br>
Regards,<br>
<font color="#888888"> &nbsp;Michael Karcher<br>
<br>
<br>
</font></blockquote></div><br>