Re: [PyOpenGL-Users] OS-X build status?

[Mike C. F. <mcf...@ro...>]

A new (source) distribution is definitely one of the things I'd like to 
see.  I've been spending the time going through the bug and issue 
trackers in hopes of allowing Rene to do a new release (including both 
binary and source distros) soon.  There is now a major memory leak fixed 
for all platforms, so it would be very good to make the package 
available with that fix.

Regarding including the SWIG wrappers in CVS, it gets messy (basically 
every time I build they get changed). That's not horrifically bad, but 
it's annoying (5MB of generated files needing to be uploaded to CVS for 
every change).  :(  Still, if there's real need for this, I suppose we 
could do it.  All-in-all I'd rather include them in source distros only 
(and maybe even have them be optional in those, possibly distributed as 
an add-on .zip file).

BTW, no need to appologize regarding delays, I work on PyOpenGL only 
sporadically (a few weeks every 4-6 months, when I run through the issue 
trackers looking for low-hanging fruit I can pick off) so even a 
multi-month delay often isn't noticable to me ;) .

I'll look at the patch sometime this evening to see if anything jumps 
out at me, but realistically, I have no clue what Apple/OS-X needs 
(never even touched an OS-X mouse, let alone built something on one). It 
would be helpful if other Apple people could check, apply, test and 
comment on the patch.  I'm not exactly a PTB, but I do have check-in 
privileges (for the time being :) ), so if there's a general consensus 
(or even a silence of sufficient length), I'll check it in.

Enjoy,
Mike

Jack Jansen wrote:

>
> On zaterdag, dec 28, 2002, at 06:49 Europe/Amsterdam, Mike C. 
> Fletcher  wrote:
>
>> I notice that there's a darwin.cfg in the PyOpenGL2 config 
>> directory,  and also that there is an open bug report regarding 
>> building on OS-X  the comments on which suggest there's a need for a 
>> .cfg.  I'm guessing  the bug-report is now stale, but if I close it 
>> I'll likely just need  to open another for "doesn't build on OS-X".  
>> Any of the OS-X types  want to give me a heads-up on what the current 
>> status of PyOpenGL on  OS-X is?
>>
>> http://sourceforge.net/tracker/ 
>> index.php?func=detail&aid=544084&group_id=5988&atid=105988
>
>
> I've attached my patch to the error report. Sorry for sitting on this  
> for so long, but I was too busy with other things.
>
> Now it's up to the powers-that-be to check the patch and hopefully  
> apply it. I would also like to make a case for doing a new  
> distribution. Without a new source distribution PyOpenGL is basically  
> unusable on MacOSX, unless you build from CVS. And building from CVS 
> is  a horrendous experience, because the swig output files are not in 
> CVS,  _and_ swig is a fast-moving target, _and_ you need to get the 
> exact  right version of swig to have any success building PyOpenGL. 
> Actually,  I would also like to make a case for including the 
> swig-generated files  in CVS. I do the same for MacPython toolbox 
> modules, and it's a boon  for people who aren't interested in hardcore 
> development of the package  itself but just want to be on the bleeding 
> edge.
> -- 
> - Jack Jansen        <Jac...@or...>         
> http://www.cwi.nl/~jack -
> - If I can't dance I don't want to be part of your revolution -- Emma  
> Goldman -
>
...

_______________________________________
  Mike C. Fletcher
  Designer, VR Plumber, Coder
  http://members.rogers.com/mcfletch/