According to http://www.py2exe.org/index.cgi/Tutorial#Step51 , msvcr71.dll is from VS 2005, while python 2.6 and newer use VS 2008 (and hence msvcr90.dll). Since I'm on python 2.7, it should be using msvcr90.dll, not 71. :-/ I guess I should have included that in my original email. I guess I'm trying to ask "why does PyOpenGL ask for a .dll that's clearly out of date with respect to the python version that I'm using?"
You can install the MSVS 2008 Express Edition for free; that's what I've done and it works fine (for example, we also use a lot of Cython, and it uses VS 2008).
i think the dll comes from visual studio 2005 or 2008. The newer versions of python do not come with these files I think. It gave me trouble trying to install python on windows 7 so I am stuck using python on my laptop with windows xp since my laptop has visual studio.
On Tue, Feb 8, 2011 at 12:00 PM, Eli Stevens (Gmail) <email@example.com> wrote:
When I import OpenGL.GL like this under windows XP:
Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import OpenGL.GL
I get the following error in an alert box:
python.exe - Unable To Locate Component
This application has failed to start becuase MSVCR71.dll was not found. Re-installing the application may fix this problem.
The same behavior occurs when trying to import OpenGL.GL from inside our application, however, aside from the alert box, the application seems to run fine (we're able to use OpenGL just fine, see 3d stuff, shaders, etc. etc.).
PyOpenGL was installed via easy_install:
Any suggestions on what we need to do to get this (seemingly spurious) alert to go away?
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
PyOpenGL-Users mailing list