On 4/19/2012 23:56, Kai Tietz wrote:
> 2012/4/19 JonY :
>> On 4/19/2012 19:51, MARTIN Pierre wrote:
>>> Dear JonY,
>>>
Fastcall and stdcall are different call conventions, so don't mix them up.
>>> i know, but i tried to see what happenned.
>>>
Seeing your earlier gendef output, _ZN7TotoL
2012/4/19 JonY :
> On 4/19/2012 19:51, MARTIN Pierre wrote:
>> Dear JonY,
>>
>>> Fastcall and stdcall are different call conventions, so don't mix them up.
>> i know, but i tried to see what happenned.
>>
>>> Seeing your earlier gendef output, _ZN7TotoLibC1Ev@4@4 looks very wrong,
>>> how are you b
On 4/19/2012 19:51, MARTIN Pierre wrote:
> Dear JonY,
>
>> Fastcall and stdcall are different call conventions, so don't mix them up.
> i know, but i tried to see what happenned.
>
>> Seeing your earlier gendef output, _ZN7TotoLibC1Ev@4@4 looks very wrong,
>> how are you building the DLL? Maybe y
Dear JonY,
> Fastcall and stdcall are different call conventions, so don't mix them up.
i know, but i tried to see what happenned.
> Seeing your earlier gendef output, _ZN7TotoLibC1Ev@4@4 looks very wrong,
> how are you building the DLL? Maybe you can pass me the source/headers
> off-list.
i did!
On 4/19/2012 09:10, MARTIN Pierre wrote:
> i just tried replacing all __stdcall on my example by __fastcall, and rebuilt
> the test library, re-made the .def / .delayed.a etc. Then the main executable
> can link against the library (Although, the .def looks exactly the same to
> me...), but it c
