stefan at codeweavers.com
Sun Jul 6 21:13:59 CDT 2008
Yes, this guide is reasonable, except probably the building part. You *may*
want to write this DLL as part of Wine, although I am afraid that we don't
have a policy how to deal with non-Windows DLLs(since cuda is an Nvidia
thing, not from MS). Of course the 5.5 part doesn't apply then as well.
From: wine-devel-bounces at winehq.org [mailto:wine-devel-bounces at winehq.org]
On Behalf Of Seth Shelnutt
Sent: Sunday, July 06, 2008 6:29 PM
To: Michael Karcher
Cc: wine-devel at winehq.org
Subject: Re: CUDA wrapper
I writing a wrapper, would it be correct to more or less follow this guide,
on winelib dll's? http://www.winehq.org/site/docs/winelib-guide/bindlls
I'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
I'll be looking at that opengl32 perl script because there is 102 pages of
functions that cudart.dll and libcudart.so both contain.
On Sun, Jul 6, 2008 at 6:53 PM, Michael Karcher
<wine at mkarcher.dialup.fu-berlin.de> wrote:
This is not going to work. PE style dynamic linking works quite
different from ELF style dynamic linking. Wine can not link native ELF
libraries to windows applications. The .dll.so files from wine are
special in being ELF files but containing extra information that allows
the Wine dynamic linker to link it into PE processes.
This is right. You need at least a correct .spec file to make a wine
dll. You still have to implement a wrapper for each function, as Windows
usually uses the stdcall calling convention, whereas linux uses cdecl by
default. There might be some way to automate writing the wrapper
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wine-devel