Thread: [PyOpenGL-Devel] Need for VC++ compiler (or Mingw32 fixes)
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@ro...> - 2002-12-31 11:54:37
|
I'd like to be able to do a public beta some time in the next few weeks (there are now a number of significant fixes in CVS), however I still don't have access to a VC++ I can use for the build, and Mingw32 is not able to build the current CVS tree. As a result, I can't do a release myself. Rene had mentioned the possibility that if he got frustrated enough with Mingw32 he might buy VC++ (I know I'm seriously frustrated with it, did you go postal and buy it, Rene?) I'm not really in a position to be buying software just now (unemployed at the moment), so I'm wondering if one of the developers with VC++ would be willing to act as the Win32 packager for the project? How I see it working: I (or Rene) can do the .zip and .tar.gz source distros, and then the Win32 packager can compile that and create a bdist_wininst for each of the supported Python versions (1.5.2, 2.0, 2.1, 2.2, and possibly 2.3). The packager would need to set up each Python version, OpenGL, GLU, GLUT and Tkinter 8.3 w/ import libraries (I'll work on a document explaining the full requirements/steps for building). For those interested in Mingw32: MingW is choking on name-matching, the only doc I can find on the error I'm seeing suggests that the "solution" is to manually edit every symbol name to match what's expected. Yech. http://sebsauvage.net/python/mingw.html pointing to: http://www.emmestech.com/software/cygwin/pexports-0.43/moron1.html examples of failure reports: build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x1540):interface_util.c: undefined reference to `glPixelStorei@8' build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x154c):interface_util.c: more undefined references to `glPixelStorei@8' follow build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x15ca):interface_util.c: undefined reference to `_imp__PyString_Size' Sigh. Enjoy all, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
From: <il...@ya...> - 2003-01-02 09:58:29
|
--- "Mike C. Fletcher" <mcf...@ro...> wrote: > I'd like to be able to do a public beta some time in > the next few weeks > (there are now a number of significant fixes in > CVS), however I still > don't have access to a VC++ I can use for the build, > and Mingw32 is not > able to build the current CVS tree. As a result, I > can't do a release > myself. > > Rene had mentioned the possibility that if he got > frustrated enough with > Mingw32 he might buy VC++ (I know I'm seriously > frustrated with it, did > you go postal and buy it, Rene?) I went postal :) Haven't bought it yet, I'll look into prices tomorrow. >I'm not really in > a position to be > buying software just now (unemployed at the moment), Good luck with your job hunting :') > so I'm wondering if > one of the developers with VC++ would be willing to > act as the Win32 > packager for the project? > > How I see it working: > I (or Rene) can do the .zip and .tar.gz source > distros, and then the > Win32 packager can compile that and create a > bdist_wininst for each of > the supported Python versions (1.5.2, 2.0, 2.1, 2.2, > and possibly 2.3). > The packager would need to set up each Python > version, OpenGL, GLU, > GLUT and Tkinter 8.3 w/ import libraries (I'll work > on a document > explaining the full requirements/steps for > building). > > For those interested in Mingw32: > MingW is choking on name-matching, the only doc > I can find on the > error I'm seeing suggests that the "solution" is to > manually edit every > symbol name to match what's expected. Yech. > > http://sebsauvage.net/python/mingw.html pointing > to: > > http://www.emmestech.com/software/cygwin/pexports-0.43/moron1.html > > examples of failure reports: > > build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x1540):interface_util.c: > > undefined reference to `glPixelStorei@8' > > build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x154c):interface_util.c: > > more undefined references to `glPixelStorei@8' > follow > > build\temp.win32-2.2\libinterface_util.a(interface_util.o.b)(.text+0x15ca):interface_util.c: > > undefined reference to `_imp__PyString_Size' > Might not be too hard to write a script to extract the symbol errors, then make the necessary changes to the def file. Perhaps I'll give that a go tomorrow when I recover from the week long heavy drinking session I had at the woodford folk festival. __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
From: Mike C. F. <mcf...@ro...> - 2003-01-02 11:41:31
|
Rene Dudfield wrote: > --- "Mike C. Fletcher" <mcf...@ro...> wrote: > > > ... >>Rene had mentioned the possibility that if he got >>frustrated enough with >>Mingw32 he might buy VC++ (I know I'm seriously >>frustrated with it, did >>you go postal and buy it, Rene?) >> >> > > >I went postal :) Haven't bought it yet, I'll look into >prices tomorrow. > Very cool. >Good luck with your job hunting :') > Thanks :) . >Might not be too hard to write a script to extract the > symbol errors, then make the necessary changes to the >def file. Perhaps I'll give that a go tomorrow when I >recover from the week long heavy drinking session I >had at the woodford folk festival. > I considered that, but... well... yech :) . Especially since people would need to run that script to build with mingw32 for their local version of Python and MingW32 (i.e. we'd probably need to distribute it). Really seems like a problem that the MingW people would want to fix rather than us. Oh well. If you want to play with it that's cool, who knows, maybe whatever you come up with will become part of MingW. Okay, think I'll head to bed, spent the night writing documentation, and that always tires me out :) . Have fun, Mike |