Re: Compiling Protocol-Plugin c++ (MinGW)

Hello,

thx for the reply, but I've already tested that.

The problem seems to be with my configuration and/or Pidgin/Windows 
handling dll files compiled with c++.

I'm testing under Windows 7 (running within a vm) and it crashes there 
on exiting when Pidgin calls  the DestroyWindow-function in 
gtkwin32dep.c:440.

On Windows 10 it does not happen. It looks like it doesn't have that 
issue. But still, when you are starting Pidgin from command-line it will 
not return to the command-line after exiting Pidgin.

I've tested that with another plugin written in c++ and it has exactly 
the same issue, as much as my mini-plugin (the one posted on pastebin -> 
http://pastebin.com/WbNy1nMr) I've written to show the bug.

Best regards,

farci



Am 10.11.2016 um 20:17 schrieb Ethan Blanton:
> Farc wrote:
>> I've uploaded the source to github: https://github.com/farcdev/spinp
> I know this is an ancient thread, but I'm just getting to it.
>
> You're doing all kinds of illegal runtime stuff.  Every single symbol
> that you put into spinp_protocol_info needs to be extern "C".  This is
> probably why your plugin is crashing.
>
> Ethan

_______________________________________________
Devel mailing list
[email protected]
https://pidgin.im/cgi-bin/mailman/listinfo/devel