Installing on Windows with 2.7 about hoep HOT 3 CLOSED

Can you follow the steps in this guide and let me know if that solves the issue?

from hoep.

Thanks, but unfortunately to no avail. I can now see in the output that the call to MinGW no longer includes "-mno-cygwin" flags, but still get the same error messages. Also resintalled MinGW, but no change.

C:\MinGW\bin\gcc.exe -shared -s build\temp.win32-2.7\Release\ext\py2k\hoep.o build\temp.win32-2.7\Release\ext\py2k\wrapper.o build\temp.win32-2.7\Release\ext\hoedown\autolink.o build\temp.win32-2.7\Release\ext\hoedown\buffer.o build\temp.win32-2.7\Release\ext\hoedown\document.o build\temp.win32-2.7\Release\ext\hoedown\escape.o build\temp.win32-2.7\Release\ext\hoedown\html.o build\temp.win32-2.7\Release\ext\hoedown\html_blocks.o build\temp.win32-2.7\Release\ext\hoedown\html_smartypants.o build\temp.win32-2.7\Release\ext\hoedown\stack.o build\temp.win32-2.7\Release\ext\hoedown\version.o build\temp.win32-2.7\Release\ext\py2k\hoep.def -LC:\Python27\libs -LC:\Python27\PCbuild -lpython27 -lmsvcr90 -o build\lib.win32-2.7\hoep.pyd

from hoep.

I solved this by following the instructions on this blog:

http://eli.thegreenplace.net/2008/06/28/compiling-python-extensions-with-distutils-and-mingw/

In short, MinGW needs a pythonXX.a file as Python's export lib isn't good enough for it... Took a lot of digging before I found that, but that's my issue resolved and it's nothing to do with Hoep so case closed. Thanks for looking into it though.

from hoep.