F%#k, f%#k, f%#k ;)
Thanks for testing that out. I'll try and get
pyopengl working with the latest swig when the new
latest swig (.16) is released.
I'll put a README.swig_version in there too I think,
so we know which version of swig to use. Since as you
say, swig seems to change in mysterious ways every
--- Jack Jansen <Jack.Jansen@...> wrote: > To
follow up on my own posting (in case someone else
> runs afoul of
> this): I made the problem disappear by using SWIG
> 1.3.13. It's a
> [expletive deleted] shame that SWIG seems to have
> incompatibilities between almost every two micro
> On Monday, Oct 14, 2002, at 14:56 Europe/Amsterdam,
> Jack Jansen wrote:
> > I'm trying (again) to build PyOpenGL from source
> (from the current CVS
> > head), and after a few problems that I managed to
> fix I'm now stuck.
> > There seems to be confusion over the name of the C
> extension module,
> > sometimes it's referred to as __init___ and
> sometimes as ___init__.
> > For instance, site-packages/OpenGL/GL/__init__.py
> tries to import
> > ___init__. But the code then uses ___init__ in
> some places, __init___
> > in others. I assume this is some sort of a swig
> mixup, but I haven't a
> > clue how to fix it.
> > I'm using PyOpenGL from the CVS repository, SWIG
> 1.3.15 (the most
> > recent version). This is on Redhat Linux (kernel
> version 2.4.18).
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts