DLL-building griefs

[Niki Spahiev]

29.10.2000, 15:08:07, Will Ware wrote:

WW> I'm trying to build a DLL (previously using Cygwin, now using Mingw)
WW> for a Python module. My batch file looks like this:

WW> gcc -Ic:\Python20\Include -c foo.c
echo EXPORTS >> foo.def
WW> nm foo.o | grep " T _" | sed "s/.* T _//" >> foo.def
WW> dllwrap --def foo.def --base-file foo.base --output-exp foo.exp \
WW>    --dllname foo.dll foo.o

WW> During the execution of dllwrap.exe, I get complaints that various
WW> functions are undefined: PyArg_ParseTuple, Py_BuildValue, and
WW> Py_InitModule4. As a result, the DLL never gets built.

WW> My experience with Unix while building .so files has been that the
WW> linker is willing to assume that these references would be resolved
WW> when the .so file was invoked by, say, being imported by Python.
WW> Is it possible for references to remain unresolved during the build
WW> process in Windows, or is this a fatal flaw in everything Windows-ish?

These are in pythonXX.dll so you should include puthonXX.lib for
linker to be happy.

-- 
Best regards,
 Niki Spahiev