Undefined calling conventions in Python.h

Fredrik Lundh fredrik at pythonware.com
Wed Jul 23 09:59:48 CEST 2008


Jaco Naude wrote:

> 1>application.obj : error LNK2031: unable to generate p/invoke for
> "extern "C" void __clrcall Py_Exit(int)" (?Py_Exit@@$$J0YMXH at Z);
> calling convention missing in metadata
> 1>frmPythonInterface.obj : error LNK2031: unable to generate p/invoke
> for "extern "C" void __clrcall Py_Exit(int)" (?Py_Exit@@$$J0YMXH at Z);
> calling convention missing in metadata
> 
> I'm probably missing something but I can't find any calling convention
> details in Python.h or the other headers included in this file.

the precence of name mangling indicates that your compiler doesn't
understand that Python's a C library, and therefore uses C calling
conventions.  have you managed to override the defaults in some odd
way?

</F>




More information about the Python-list mailing list