Re: Compiling extension with Visual C++ Toolkit Compiler - MSVCR80.dll

2007-01-30 Thread alexandre_irrthum
Thanks for your answers Martin and Peter, I figured out why python.exe was asking for MSVCR80.dll. The first time I compiled the library, MS Visual C++ Express 2005 was used during the build (despite my PATH pointing to MS Visual C++ Toolkit 2003). When I removed Express 2005, I forgot to remov

Re: Compiling extension with Visual C++ Toolkit Compiler - MSVCR80.dll

2007-01-29 Thread Peter Wang
On Jan 29, 2:47 pm, [EMAIL PROTECTED] wrote: > The library seems to build correctly (producing Polygon.py and > cPolygon.pyd), but when I import it I get the following message from > python.exe: "This application has failed to start because MSVCR80.dll > was not found". I thought that this might be

Re: Compiling extension with Visual C++ Toolkit Compiler - MSVCR80.dll

2007-01-29 Thread Martin v. Löwis
[EMAIL PROTECTED] schrieb: > The library seems to build correctly (producing Polygon.py and > cPolygon.pyd), but when I import it I get the following message from > python.exe: "This application has failed to start because MSVCR80.dll > was not found". I thought that this might be due to Python