Interface Calling conventions
Posted: 03 Oct 2009, 03:55
Right now there is a problem regarding Visual studio AIs vs Mingw32 spring builds.
I am struggling to get the correct exports on ym AI, I cannot get a function name handleevent using stdcall that doesnt have an @ and a number on the end.
e.g. _handleEvent@12
To get the AI t interface with spring at all requires a change which zerver reverted because it broke visual studio builds of spring, in exportdefines.h, but to get the required function names exported needs cdecl, which won't work and generates debugger messages after startup and other undefined behaviour
I'm using visual studio 2008, using mingw32 is not an option for me. I currently have deadlines to make, and this si my nubmer one stalling block for all future development at the moment.
I am struggling to get the correct exports on ym AI, I cannot get a function name handleevent using stdcall that doesnt have an @ and a number on the end.
e.g. _handleEvent@12
To get the AI t interface with spring at all requires a change which zerver reverted because it broke visual studio builds of spring, in exportdefines.h, but to get the required function names exported needs cdecl, which won't work and generates debugger messages after startup and other undefined behaviour
I'm using visual studio 2008, using mingw32 is not an option for me. I currently have deadlines to make, and this si my nubmer one stalling block for all future development at the moment.