Re: OpenGL.xs improvements

Hi Geoffrey (or 'f),

Sorry I can't answer your questions && don't have commit bits to give
out but I do have an AMD64 Gentoo GNU/Linux machine with dual nVidia
6800GTs, binary 'nvidia' XOrg drivers with my 2.6.12-r6 kernel, and
Perl 5.8.8.  I'd be glad to help test your updates.  I've also got a
Vaio Core Duo laptop running WindowsXP with what I'm pretty sure is an
nVidia 7400 Go for video/3D acceleration and a recent ActiveState Perl
on there (probably 5.8.7).  Sorry I can't help with any PPC Mac stuff
either but I'd be glad to assist in SDL_Perl patch-testing, switching
to GLEW, etc. however I can.  Please let me know.  Thanks.

[email protected]
HTTP://PipForPresident.Org

On 4/27/07, Geoffrey Broadwell <[email protected]> wrote:
> nVidia's latest drivers are finally in Debian unstable and wending their
> way to testing; meanwhile I've come across more functionality that I
> need and is missing from OpenGL.xs in SDL_perl 1.x.  And of course
> OpenGL.pm is turning up the friendly competition by suddenly adding
> support for lots of new stuff after being unchanged for a great while.
> It seems the time has finally come to start the oft-delayed merge of my
> "OpenGL fixes for 1.x" tree into the official SDL_Perl 2.x tree.
>
> I've pulled a copy of the latest SVN version (r26 as I write this) and
> have started looking around to understand the build system and other
> changes since 1.x.  At this point, I've got a few questions before I get
> started with the meat of the merge:
>
> 1. Where can I find the scripts/ directory containing the constant
> module generators (gl_const.pl, sdl_const.pl, and so on)?
>
> 2. Do you prefer updates in the form of emails containing inline
> patches, emails with patch attachments, or direct svn commits?
>
> 3. If svn commits are preferred, how do I register for a commitbit?
>
> 4. Do you prefer each patch/commit to be exactly one change, or are
> multiple simultaneous changes allowed if they are all small?
>
> 5. Would you accept a patch/commit reordering the functions in
> OpenGL.xs, either to pure alphabetical, or by GL/GLU version and then
> alphabetically?  (This is not a requirement for me to do the other
> merges, but it makes it much easier to make sure everything is complete
> when comparing against the OpenGL references.  Plus it's just nice to be
> able to find things easily when working in the source ....)
>
> 6. Any objection to switching from ifdef for various GL/GLU versions to
> one of the standard extension loader libraries such as GLsdk, GLee, or
> GLEW?  (Right now I'm leaning towards GLEW because it seems to be equal
> or favored by the ARB, Khronos, and nVidia.)  Among other things this
> would allow the builds to be independent of borken system headers, and
> properly handle runtime GL/GLU versions not matching compile time,
> important for packaged versions of SDL_Perl.
>
> 7. I would be doing primary work on Debian testing, i686 and amd64.  I
> also have access to a Mac G4 running 10.3.9 that I can use to test my
> changes for portability, but I have no Mac compiling skills.  Anyone
> have directions for getting everything necessary to compile SDL_Perl
> installed/built on a PPC Mac?
>
>
> -'f