On Sat, 2006-09-09 at 22:41 -0500, Matthias Miller wrote: > socket is defined as WINSOCK_API_LINKAGE SOCKET PASCAL > socket(int,int,int). The import piece is PASCAL, which is defined as > __stdcall. The calling convention changes the name decoration of the > exported function.
Ah, OK, the stdcall/cdecl thing. I'm not sure how best to handle this. Does *every* function which the configure script checks for on MinGW use the __stdcall calling convention, or only some? If only some, would it be possible to use some global toggle which switches what NE_SEARCH_LIBS will check for? e.g. NE_MINGW_STDCALL NE_SEARCH_LIBS(socket, ...) NE_MINGW_CDECL NE_SEARCH_LIBS(somethingelse, ...) would that make sense? Then NE_SEARCH_LIBS could just use some global variable to prefix the function in the AC_LINK_IFELSEs. And this could all be conditional on `uname -s` being whatever MinGW defines at some point. Does that sound workable? > Would you like for me to come up with another patch for this? That would be great, yes please! joe _______________________________________________ neon mailing list [email protected] http://mailman.webdav.org/mailman/listinfo/neon
