Thread: [PyOpenGL-Devel] Something's wrong in the state of Denmark...
Brought to you by:
mcfletch
From: Mike C. F. <mcf...@ro...> - 2003-10-06 02:00:18
|
Well, so much for just dropping in a few patches and declaring the next version. Been tracking down various build errors all day, only to finally get it building and find a crash with the glVertexPointerd function. Sigh. Looks like I'll need to put aside some more time for this next weekend. I don't even recall checking in any changes since 2.0.1.04 (I was building to test my new OS + compiler setup before trying to integrate the Mac patches), but something must have changed. Oh well, another week won't kill anyone I suppose, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
From: Mike C. F. <mcf...@ro...> - 2003-10-12 10:16:44
|
Well, happy news: PyOpenGL builds again on my Win32 setup, and appears to be fully functional. Unhappy news: AFAICS, nothing I changed should have had the slightest effect. I'm suspicious that the whole failing build set was just a matter of having some old (compiled) code hanging around that was getting mixed into the new build. I'm even more suspicious that it may have been the auto-build environment itself causing the problems (i.e. by creating a mix of Numpy versions, as it stores the build directories for the different versions in the same place). I wound up having to disable Togl even for Python 2.2, as it's failing on my machine with message that it can't load the Tk 8.1 package. I'll work on re-enabling it tomorrow. Tomorrow's plan: * Switch back to non-debug builds and re-test * Build under the autobuild script and re-test * Integrate OS-X patches * Go through bug-reports looking for anything which can be fixed easily (and fix it) * Get a working Linux installation (Knoppix most likely) and try to compile under that * Rebuild the docs in case anything has changed (don't believe it has, actually) * Create a release candidate source .tar.gz and .zip, RPM as well (though that'll require a Red Hat install IIUC) * Maybe answer some email on the user-list :) Night all, Mike Mike C. Fletcher wrote: > Well, so much for just dropping in a few patches and declaring the > next version. Been tracking down various build errors all day, only > to finally get it building and find a crash with the glVertexPointerd > function. Sigh. Looks like I'll need to put aside some more time for > this next weekend. I don't even recall checking in any changes since > 2.0.1.04 (I was building to test my new OS + compiler setup before > trying to integrate the Mac patches), but something must have changed. > > Oh well, another week won't kill anyone I suppose, > Mike |
From: Mike C. F. <mcf...@ro...> - 2003-10-13 01:07:17
|
Mike C. Fletcher wrote: > Tomorrow's plan: > > * Switch back to non-debug builds and re-test Works fine. > * Build under the autobuild script and re-test This does appear to have been the problem, was building each version for a given Python version in the same directory. Result was that the code would get compiled for the wrong Numpy version. This should now be fixed permanently. Rest is still on the plate... > * Integrate OS-X patches > * Go through bug-reports looking for anything which can be fixed > easily (and fix it) > * Get a working Linux installation (Knoppix most likely) and try to > compile under that > * Rebuild the docs in case anything has changed (don't believe it > has, actually) > * Create a release candidate source .tar.gz and .zip, RPM as well > (though that'll require a Red Hat install IIUC) > * Maybe answer some email on the user-list :) but the night is still young. I'm seeing some weird pygame parachute faults that almost seem like the weakref bug fixed in Python 2.2.2 rearing it's head again, but that only affects OpenGLContext, not core PyOpenGL, so shouldn't delay the release. Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |
From: Mike C. F. <mcf...@ro...> - 2003-10-14 06:32:54
|
Mike C. Fletcher wrote: >> * Get a working Linux installation (Knoppix most likely) and try to >> compile under that > Well, that was a bad decision. Beyond messing up my master boot record (the install script is very primitive), turns out that (once I got it all fixed and installed), Knoppix is a royal pain for installing any SWIG other than the one in apt (AFAICS, though I'm obviously a bit of a newbie with Debian administration). The versions I was able to find were all patched extensively enough to make it pretty unlikely that I'll get the time to work it through, but I spent quite a while trying to figure out how it should work. So, next weekend I'll either have to generate the wrappers on Win32 or re-install Red Hat and build there. Blah. Yet more delays. Oh, I integrated one of Andrew Straw's patches, then SF stopped working for a while, so I switched to the Unix install task. A few more patches to go still. Night all, Mike _______________________________________ Mike C. Fletcher Designer, VR Plumber, Coder http://members.rogers.com/mcfletch/ |