Hi,
The Dll exports its function names using the __stdcall decorations e.g.
_getlibraryvers...@0. Windows OS Dlls also provide an undecorated name
(GetLibraryVersion) which winedump expects. While it would be easy to fix
winedump I'm not sure this would suffice. Especially I don't know if it's
act
On Sat, Aug 22, 2009 at 11:17 AM, Juan Lang wrote:
>> 1) Creating a vendor.def file doesn't work. The resulting file has an empty
>> EXPORTS section:
>>
>> winedump spec vendor.dll
>> winebuild --def -E vendor.spec -o vendor.def
>
> That seems to mean winedump isn't parsing this right, or that it t
> I have a windows dll without source code (vendor.dll) that I want to use in
> a winelib application.
>
> 1) Creating a vendor.def file doesn't work. The resulting file has an empty
> EXPORTS section:
>
> winedump spec vendor.dll
> winebuild --def -E vendor.spec -o vendor.def
That seems to mean w
Thomas Trummer schrieb:
> Hi,
>
> I have a windows dll without source code (vendor.dll) that I want to use
> in a winelib application.
>
> There are two problems however:
>
> 1) Creating a vendor.def file doesn't work. The resulting file has an
> empty EXPORTS section:
>
> winedump spec vendor.
Hi,
OK, a minute after I sent the mail I figured out number two:
For vendor.dll the corresponding .def file has to be called libvendor.def.
I still need help with point one, though.
Thomas
Hi,
I have a windows dll without source code (vendor.dll) that I want to use in
a winelib application.
There are two problems however:
1) Creating a vendor.def file doesn't work. The resulting file has an empty
EXPORTS section:
winedump spec vendor.dll
winebuild --def -E vendor.spec -o vendor.d
