Re: [PyOpenGL-Users] PyOpenGL on Windows

[Chris B. <Chr...@no...>]

On 7/5/11 9:54 AM, Alejandro Segovia wrote:
>     As a rule, it is easiest, and maybe necessary, to build python
>     extensions on Windows with the same version of the MS compiler used to
>     build the python binary. AFAIK, it's CRT issues.

> I'm using Python 2.7 on Windows 7 x64. It is the python.org
> <http://python.org> build.

then I am surprised that there aren't issues with that older CRT.

> If you haven't run across this issue, it might be because you have
> MSVCRT7.1.dll in your system.

probably do -- it's pretty darn common. I've generally not bothered to 
distribute it with py2exe projects, as most people have it. (or did -- 
it maybe getting less common with Win7 systems, etc)

> I do understand you point, however.
> Perhaps providing a gle32.dll linked against MSVCRT90 could be a problem
> for people running older versions of Python (2.4 and 2.5).

it might, yes - certainly testing would be in order.

> I have noticed other Python projects usually keep different binary
> downloads for different versions of Python.

yes -- that's generally required -- as a rule, the different versions of 
python are not binary compatible, so you need to do that, CRT issues 
aside. I guess if you use ctypes as your only interface, you avoid that.

> This is all assuming gle32 is at all needed as a part of PyOpenGL. If
> it's not used internally, maybe it shouldn't come with PyOpenGL, as the
> whole linking issue seems to be confusing enough for at least one person :)

indeed -- that would simplify things.

-Chris


-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...