pyopengl-users — Discussion of all PyOpenGL matters.

Re: [PyOpenGL-Users] Modelview and projection matrices

[Richard J. <ric...@op...>]

On Sat, 5 Jan 2002 23:46, Jan Ekholm wrote:
> Hi,
>
> I've been trying to implement some form of view frustum culling. I found
> some interesting code on:
>
> 	http://www.markmorley.com/opengl/frustumculling.html
>
> The code is in C, so I need to translate it to Python. Central in that
> approach is the use the current modelview and projection matrices. So I
> get the using:
>
>         projection = glGetFloatv ( GL_PROJECTION_MATRIX )
>         modelview  = glGetFloatv ( GL_MODELVIEW_MATRIX )
>
> However, the Python versions return a [4][4] matrix, while the C versions
> return a [16] array. The code on the page above uses a [16] array for all
> indexing, so I'd like to translate the matrices I get from glGetFloatv to
> arrays.

Code (interchangeable python and C modules for frustum culling and octree 
storage) attached :)

You can also get this code by downloading the tarball from 
http://goanna.adroit.net/~richard/ufo/ where there is some octree code that 
uses the frustum culling too. Note that since I discovered that the code is 
_significantly_ faster when it just draws _everything_ rather than tries to 
cull, the current ufo.py doesn't actually call the frustum or octree code. In 
a nutshell, define objects like the triangle object, stuff them into the 
octree with octree.insertPolygon or octree.insertObject for each of the 
object's bounding vertexes. The call octree.render with the frustum and it 
calls each of the appropriate sub-object's render() method.

Note that I do _all_ my view projection manipulation in the projection 
matrix, so I don't include the modelview matrix. It's simple enough to 
un-comment the appropriate code though.


    Richard

[PyOpenGL-Users] Modelview and projection matrices

[Jan E. <ch...@in...>]

Hi,

I've been trying to implement some form of view frustum culling. I found
some interesting code on:

	http://www.markmorley.com/opengl/frustumculling.html

The code is in C, so I need to translate it to Python. Central in that
approach is the use the current modelview and projection matrices. So I
get the using:

        projection = glGetFloatv ( GL_PROJECTION_MATRIX )
        modelview  = glGetFloatv ( GL_MODELVIEW_MATRIX )

However, the Python versions return a [4][4] matrix, while the C versions
return a [16] array. The code on the page above uses a [16] array for all
indexing, so I'd like to translate the matrices I get from glGetFloatv to
arrays.

The problem is now that I'm not sure how the returned matrix should be
"flattened". Should I go by row or column, i.e. the first element in the
array should be [0][0], but should the second be [0][1] or [1][0] and so
on?

I have tried both ways, but my code still won't work, so I'd like to rule
out at least this possibility for error. Ny ideas?

	Chakie

-- 
 The Emperor had all the qualifications for a corpse except, as it were, the
         most vital one.
                                       -- Terry Pratchett, Interesting Times

[PyOpenGL-Users] OpenGL 2D Library

[Andy S. <an...@ne...>]

Another one worth checking out would be:

http://plib.sourceforge.net/

RE: [PyOpenGL-Users] OpenGL 2D Library

[Tarn W. B. <twb...@us...>]

There are a number of 2D libraries available.  I'd recommend looking at
these before you reinvent the wheel.

GLI http://romka.demonews.com/projects/gli/index_eng.htm
GLUI http://www.cs.unc.edu/~rademach/glui/
MUI (included with GLUT)

None of these has been wrapped for use with PyOpenGL yet.  GLUI looks
like the best one, but I will probably start with MUI since it is part
of GLUT.  From my initial investigations, I believe that wrapping will
probably be trivial.  Volunteers are always welcome.

Tarn

[PyOpenGL-Users] OpenGL 2D Library

[Jeffrey D. <jp...@ro...>]

I am developing a 2d library to be used for user interfaces to my python 
project. Do any of these exist at the moment?

And would the master of pyopengl be interested in integrating such a 
beast if it suited the library?

Regards,
Jeffrey Drake

RE: [PyOpenGL-Users] How much cleanup is my responsibility?

[Tarn W. B. <twb...@us...>]

| If I create a display list (a honking big one :) and don't 
| clean it up when 
| my program exits, is it cleaned up by pyopengl?

Nope.  You've got to do it yourself.

Tarn

[PyOpenGL-Users] How much cleanup is my responsibility?

[Richard J. <ric...@op...>]

If I create a display list (a honking big one :) and don't clean it up when 
my program exits, is it cleaned up by pyopengl?


    Richard

[PyOpenGL-Users] OpenGLContext 1.0a3 available

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

This is a bug-fix release of 1.0a2.  Bugs fixed are the setup bug (data 
files copied to wrong locations) and the filename case mismatches on 
case-sensitive systems.

Also included is the profile.py test, which demonstrates using a PyGame 
context to allow for standard Python profiling in PyOpenGL projects.

http://sourceforge.net/project/showfiles.php?group_id=5988&release_id=66619

Enjoy all,
Mike
_______________________________________
   Mike C. Fletcher
   http://members.rogers.com/mcfletch/

[PyOpenGL-Users] Fun with C modules

[Richard J. <ric...@op...>]

I've just spent a day converting some of my python classes over to C, with 
some fun results.

In a nutshell, my application (ok, game ;) stores a 64x64 map grid, two 
triangles per cell, in an octree. This is then culled for the frustum and 
rendered as lit and textured triangles. The scene I'm getting the following 
results from has 170 of the triangles from the octree being rendered.

I converted my frustum class (which has methods like calculate() and 
isCubeInFrustum()), octree class (which just stores away objects with a 
vertexes list and a render() method) and a simple lit/textured triangle 
object which has the aforementioned vertexes array and render() method. The 
python and C modules are functionally identical - they're completely 
interchangeable (making this test quite easy :) but the C modules do have 
several optimisations. For example, the C triangle class calls OpenGL 
directly, not through the python bindings. I suspect my unpacking the 
arguments to the gl calls once, when the object is created, has a large 
impact...

I took a set of timings (render 100 frames and then time the next 100 
frames), turning each of the C modules on and off:

             No C: 7fps
         C octree: 7fps
         C frusum: 8fps
       C triangle: 10fps
 C octree&frustum: 8fps
    C frustum&tri: 11fps
     C octree&tri: 26fps
              all: 41fps

Well, what strange numbers. At 41fps my "game" is quite playable. Sure, most 
of the work is done in a single call to a C module, but Python's still there 
holding it all together :)


    Richard

ps. I don't have a website at present - I'm between jobs - but I hope to have 
something set up soon so I can share this stuff.

RE: [PyOpenGL-Users] WGL: ChoosePixelFormat, CreatePIXELFORMATDESCRIPTOR

[Tarn W. B. <twb...@us...>]

You should use PIXELFORMATDESCRIPTOR()

As to the exception, this looks like a bug.  A temporary fix (build 47)
has been uploaded to http://pyopengl.sf.net/ftp

thanks,
Tarn

[PyOpenGL-Users] WGL: ChoosePixelFormat, CreatePIXELFORMATDESCRIPTOR

[Rene J. <chi...@ho...>]

Hi. The openGLDemo from Pythonwin creates a PIXELFORMATDESCRIPTOR using 
CreatePIXELFORMATDESCRIPTOR, but I can't find that call anywhere in.. well.. 
the entire universe world really. Searched everywhere.

This approach is wrong:

   Desc = PIXELFORMATDESCRIPTOR()
   Desc.xxx = yyy ...
   ChoosePixelFormat(DCHandle, Desc)

So is this:

   ChoosePixelFormat(DCHandle, PIXELFORMATDESCRIPTORPtr (Desc))

I get a 'TypeError.. Expected _p_q_const__PIXELFORMATDESCRIPTOR'
thrown in my face.

But what is right then??
Thanks in advance.

chi...@ho...


_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com

[PyOpenGL-Users] Python 2.2b2 build

[Tarn W. B. <twb...@us...>]

Just wanted let all know that I've posted a win32 build of 2.0.0.44 for
Python 2.2b2 to the SF site.

It may take a while to actually show up in the filelist as SF caches the
list.

Tarn

RE: [PyOpenGL-Users] bug+fix: multiple Opengl widget repaint causing stack underflow

[Tarn W. B. <twb...@us...>]

Sounds fine to me.  I'll it put into CVS unless a Togl wizard (which I am
not) has an objection.

thanks,
Tarn

[PyOpenGL-Users] bug+fix: multiple Opengl widget repaint causing stack underflow

[Maciej K. <ma...@dg...>]

In PyOpengl 2.0.0.44, Tk/__init__.py, proposed patch:

*** __init__.py.orig    Sun Jul  8 14:26:50 2001
--- __init__.py Mon Dec  3 16:26:26 2001
***************
*** 476,483 ****
--- 476,484 ----
                self.activate()

                glPushMatrix()                  # Protect our matrix
                self.update_idletasks()
+               self.activate()
                w = self.winfo_width()
                h = self.winfo_height()
                glViewport(0, 0, w, h)

If there is more than one Opengl widget, and all of them are exposed
at once (say, when switching desktops), it is quite likely that the
update_idletasks() call is going to result in tkExpose() being called
for one of the other Opengl widgets.  But this means that upon return
from this call the active Opengl widget has changed.  This caused
glPopMatrix() to pop the wrong stack, which every time resulted in
stack underflow, or worse.

-- 
Maciej Kalisiak|mac@] "The real art of conversation is not only to say the
dgp.toronto.edu|www.]  right thing in the right place, but also to leave unsaid
dgp.toronto.edu/~mac]  the wrong thing at the tempting moment."

Re: [PyOpenGL-Users] OpenGL.Tk documentation?

[Maciej K. <ma...@dg...>]

"Mike C. Fletcher" <mcf...@ya...> writes:

> You can also find (meagre) documentation by PyDoc at:
> 
> http://pyopengl.sourceforge.net/documentation/pydoc/OpenGL.Tk.html

Actually that's good enough for me.  I just wanted a list of
all the methods available to the object (including inherited ones),
and this is such a list.

-- 
Maciej Kalisiak|mac@] 
dgp.toronto.edu|www.] "Never make any mistaeks." -- anonymous
dgp.toronto.edu/~mac] 

Re: [PyOpenGL-Users] OpenGL.Tk documentation?

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

Tk.OpenGL is a wrapper class implemented in the python
file: 

    OpenGL/Tk/__init__.py

It wraps the functions of the "standard" Tk togl
widget with some convenience functions.  You can find
documentation on the togl widget in the PyOpenGL2
Source tree in src/Togl-1.5/Togl.html .  Note that
I've never actually used that documentation myself. 
You can also find (meagre) documentation by PyDoc at:

http://pyopengl.sourceforge.net/documentation/pydoc/OpenGL.Tk.html

Since I don't actually use Tk myself, I haven't spent
any real time tracking down better documentation yet.

Hope that helps,
Mike



--- Maciej Kalisiak <ma...@dg...> wrote:
> Hi,
> 
> Where would I be able to find out how to use the
> stuff from OpenGL.Tk
> (which I take is Togl stuff)?  I've got a few hints
> from looking at
> the Demo programs, but was interested in a more
> exhaustive list of
> capabilities, methods, etc.
> 
> -- 
> Maciej Kalisiak|mac@] 
> dgp.toronto.edu|www.] "A closed mouth gathers no
> feet."
> dgp.toronto.edu/~mac] 
> 
> _______________________________________________
> PyOpenGL Homepage
> http://pyopengl.sourceforge.net
> _______________________________________________
> PyOpenGL-Users mailing list
> PyO...@li...
>
https://lists.sourceforge.net/lists/listinfo/pyopengl-users


______________________________________________________ 
Send your holiday cheer with http://greetings.yahoo.ca

[PyOpenGL-Users] OpenGL.Tk documentation?

[Maciej K. <ma...@dg...>]

Hi,

Where would I be able to find out how to use the stuff from OpenGL.Tk
(which I take is Togl stuff)?  I've got a few hints from looking at
the Demo programs, but was interested in a more exhaustive list of
capabilities, methods, etc.

-- 
Maciej Kalisiak|mac@] 
dgp.toronto.edu|www.] "A closed mouth gathers no feet."
dgp.toronto.edu/~mac] 

RE: [PyOpenGL-Users] mui support

[Tarn W. B. <twb...@us...>]

| I haven't been able to find out whether or not the MUI
| mini ui thats included with GLUT has been made available
| for Python.  I don't see any binding for it.
|
| http://www.opengl.org/developers/code/mjktips/mui/mui.html
|
| Is there any intention to support this with PyOpenGL?

No binding yet.  I've submitted a feature request on the SF site.  I
probably won't have time for this for quite a while.  On the surface it
looks fairly straight foreward.

Tarn

[PyOpenGL-Users] mui support

[Patrick P. <pa...@de...>]

I haven't been able to find out whether or not the MUI
mini ui thats included with GLUT has been made available
for Python.  I don't see any binding for it.  

http://www.opengl.org/developers/code/mjktips/mui/mui.html

Is there any intention to support this with PyOpenGL?

Thanks,
Patrick.

RE: [PyOpenGL-Users] Code for ball and stick model

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

Numbered according to your questions...

1) On my machine (Win2K using the GLUT context), the window does update when
it is damaged.  Which context subclass are you using?  The code for this is
different under each context subclass because of the need to interface with
the user interface library's notification of damage.

2) You can find a demo in OpenGLContext/tests/saveimage.py for how you would
save images to a file (using glReadPixels then converting to a PIL image for
saving).

Have fun,
Mike

-----Original Message-----
From: pyo...@li...
[mailto:pyo...@li...]On Behalf Of Craig H
. Anderson
Sent: Thursday, November 29, 2001 13:03
To: pyo...@li...
Subject: [PyOpenGL-Users] Code for ball and stick model
...
A couple of questions.
1) gl02_testUnitCylinder.py displays as expected, but the window
    doesn't refresh if damaged.  What am I missing to get the window
    to refresh?
2) How would I dump the window image to a file?
...

[PyOpenGL-Users] Code for ball and stick model

[Craig H . A. <cr...@ho...>]

Greetings,

Here is my first attempt with PyOpenGL.
Python and PyOpenGL is great!
I wanted to make a ball and stick skeleton
animation to demo at an interview.  It appears
I won't get the job, but I got as far as code
to draw a sphere and cylinder.  The file
gl02_testUnitCylinder.py draws a box using OpenGLContext.

The full demo was going to read a BVH animation file,
generate a ball/stick skeleton and display an animation.

A couple of questions.
1) gl02_testUnitCylinder.py displays as expected, but the window
    doesn't refresh if damaged.  What am I missing to get the window
    to refresh?
2) How would I dump the window image to a file?

Thanks,
Craig H. Anderson
cr...@ho...


-- 
Craig H. Anderson

[PyOpenGL-Users] [ pyopengl-Support Requests-484774 ] cygwin build problems

[<no...@so...>]

Support Requests item #484774, was opened at 2001-11-23 00:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

Category: build
Group: v2.0
Status: Open
Priority: 5
Submitted By: John A. Turner (turner)
Assigned to: Tarn Weisner Burton (twburton)
Summary: cygwin build problems

Initial Comment:
thought I'd try PyOpenGL2 on win2k/cygwin

using cygwin 1.3.5 and the cygwin port of python 2.1.1
and a fresh CVS checkout of PyOpenGL2

first copied config/win32.cfg to config/cygwin.cfg,
since OpenGL progs compiled with cygwin's gcc use the
normal win32 libs (opengl32, glu32, etc.)

here's what the first bit of setup reports:

PyOpenGL 2.0.1.45.a1 setup

System configuration:
    Platform    = cygwin
    GL Platform = WGL
    Numeric     = 20.2.2
    Build Togl  = yes

1. first prob was that I didn't have SWIG, so I got:

swig -version
unable to execute swig: No such file or directory
swig1.3 -version
unable to execute swig1.3: No such file or directory
warning: build_w: Can't find SWIG, will just have to 
do with the existing wrapper source.

which would likely be ok except that soon after:

cc -I/usr/include/python2.1/Numeric -c _configtest.c -
o _configtest.o
unable to execute cc: No such file or directory

I didn't know how to force setup to use gcc rather than
cc, so I took the easy way out and copied
/usr/bin/gcc.exe to /usr/bin/cc.exe

that at least allowed things to progress...

2. next, saw lots of warnings about missing __init.py__
files, most in the Demo subdir

3. finally, failed with:

running build_clib
building 'interface_util' library
creating build/temp.cygwin-1.3.5-i686-2.1
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/interface_util.c -o 
build/temp.cygwin-1.3.5-i686-2.1/interface_util.o
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsFloatArray':
src/interface_util/interface_util.c:698: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsDoubleArray':
src/interface_util/interface_util.c:701: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsCharArray':
src/interface_util/interface_util.c:704: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedCharArray':
src/interface_util/interface_util.c:707: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsShortArray':
src/interface_util/interface_util.c:710: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedShortArray':
src/interface_util/interface_util.c:713: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsIntArray':
src/interface_util/interface_util.c:716: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedIntArray':
src/interface_util/interface_util.c:719: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: At top level:
src/interface_util/interface_util.c:780: warning: 
function declaration isn't a prototype
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/platform.c -o build/temp.cygwin-
1.3.5-i686-2.1/platform.o
src/interface_util/platform.c:4: warning: function 
declaration isn't a prototype
src/interface_util/platform.c: In function 
`GetPlatformExtensionsString':
src/interface_util/platform.c:7: warning: function 
declaration isn't a prototype
ar -cr build/temp.cygwin-1.3.5-i686-
2.1/libinterface_util.a build/temp.cygwin-1.3.5-i686-
2.1/interface_util.o build/temp.cygwin-1.3.5-i686-
2.1/platform.o
running build_ext
building 'GL.ARB.matrix_palette' extension
error: file 'src/interface/GL.ARB.matrix_palette.c' 
does not exist

any suggestions?

thanks in advance...

-JT


----------------------------------------------------------------------

>Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-28 13:37

Message:
Logged In: YES 
user_id=21784

This is same problem I had.  All the warnings are harmless.
It builds fine under GCC on Linux.  GCC 3.0 might fix this, 
but probably not.  Have you tried using Mingw32?  The 
cygwin build is going to be really slow anyways.

----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-28 13:17

Message:
Logged In: YES 
user_id=20477

gack - sorry

ok, got and built 1.3a5 - now gcc is horking:

gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1/Numeric -
I/usr/include/python2.1 -c 
src/interface/GL.ARB.multitexture.c -o build/temp.cygwin-
1.3.5-i686-2.1/GL.ARB.multitexture.o
In file included from src/interface/GL.ARB.multitexture.c:8:
src/interface/GL.ARB.multitexture.0101.inc: In function 
`SWIG_UnpackData':
src/interface/GL.ARB.multitexture.0101.inc:338: warning: 
`uu' might be used uninitialized in this function
src/interface/GL.ARB.multitexture.0101.inc: In function 
`SWIG_ConvertPtr':
src/interface/GL.ARB.multitexture.0101.inc:404: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc:407: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc:413: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc: At top level:
src/interface/GL.ARB.multitexture.0101.inc:700: warning: 
function declaration isn't a prototype
src/interface/GL.ARB.multitexture.0101.inc:748: warning: 
function declaration isn't a prototype
gcc: Internal compiler error: program cc1 got fatal signal 
11
error: command 'gcc' failed with exit status 1

this is cygwin 1.3.5 with gcc 2.95.3-5 - should I try
building gcc 3.0.2 or a snapshot or something?



----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-28 06:09

Message:
Logged In: YES 
user_id=21784

As I said in my previous comments, You need SWIG 1.3a5.  
SWIG 1.3.9 won't work.

----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-27 22:39

Message:
Logged In: YES 
user_id=20477

ok, went ahead and grabbed SWIG 1.3.9 and built (no probs),
then cvs-upped PyOpenGL2 and tried again

this time it choked here:

Building wrappers for GL.__init__
Generating shadow version selector
Generating C version selector
Generating wrappers for API version 0x0101
swig -python -Iinterface -shadow -DAPI_VERSION=257 -o 
src/interface/GL.__init___.0101.inc interface/GL/__init__.i
Syntax error
interface/GL/__init__.i:1006. Syntax error in input.


----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-23 08:10

Message:
Logged In: YES 
user_id=21784

You need SWIG 1.3a5 to build out of CVS.  The "cc" problem 
has been fixed in CVS, but the build still doesn't complete 
on my system due to an internal compiler error.  Before you 
do a CVS checkout be sure to move your cygwin.cfg file out 
of the way, since there is one in CVS now.

There is also a complete source code dist (no need for 
SWIG) at http://pyopengl.sf.net/ftp/PyOpenGL-
2.0.1.46.a1.tar.gz


----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-23 00:29

Message:
Logged In: YES 
user_id=20477

ugh - sorry about the formatting of the report - hope it
is understandable - if not let me know and I'll upload files
with the requisite info...


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

[PyOpenGL-Users] [ pyopengl-Support Requests-484774 ] cygwin build problems

[<no...@so...>]

Support Requests item #484774, was opened at 2001-11-23 00:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

Category: build
Group: v2.0
Status: Open
Priority: 5
Submitted By: John A. Turner (turner)
Assigned to: Tarn Weisner Burton (twburton)
Summary: cygwin build problems

Initial Comment:
thought I'd try PyOpenGL2 on win2k/cygwin

using cygwin 1.3.5 and the cygwin port of python 2.1.1
and a fresh CVS checkout of PyOpenGL2

first copied config/win32.cfg to config/cygwin.cfg,
since OpenGL progs compiled with cygwin's gcc use the
normal win32 libs (opengl32, glu32, etc.)

here's what the first bit of setup reports:

PyOpenGL 2.0.1.45.a1 setup

System configuration:
    Platform    = cygwin
    GL Platform = WGL
    Numeric     = 20.2.2
    Build Togl  = yes

1. first prob was that I didn't have SWIG, so I got:

swig -version
unable to execute swig: No such file or directory
swig1.3 -version
unable to execute swig1.3: No such file or directory
warning: build_w: Can't find SWIG, will just have to 
do with the existing wrapper source.

which would likely be ok except that soon after:

cc -I/usr/include/python2.1/Numeric -c _configtest.c -
o _configtest.o
unable to execute cc: No such file or directory

I didn't know how to force setup to use gcc rather than
cc, so I took the easy way out and copied
/usr/bin/gcc.exe to /usr/bin/cc.exe

that at least allowed things to progress...

2. next, saw lots of warnings about missing __init.py__
files, most in the Demo subdir

3. finally, failed with:

running build_clib
building 'interface_util' library
creating build/temp.cygwin-1.3.5-i686-2.1
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/interface_util.c -o 
build/temp.cygwin-1.3.5-i686-2.1/interface_util.o
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsFloatArray':
src/interface_util/interface_util.c:698: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsDoubleArray':
src/interface_util/interface_util.c:701: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsCharArray':
src/interface_util/interface_util.c:704: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedCharArray':
src/interface_util/interface_util.c:707: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsShortArray':
src/interface_util/interface_util.c:710: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedShortArray':
src/interface_util/interface_util.c:713: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsIntArray':
src/interface_util/interface_util.c:716: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedIntArray':
src/interface_util/interface_util.c:719: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: At top level:
src/interface_util/interface_util.c:780: warning: 
function declaration isn't a prototype
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/platform.c -o build/temp.cygwin-
1.3.5-i686-2.1/platform.o
src/interface_util/platform.c:4: warning: function 
declaration isn't a prototype
src/interface_util/platform.c: In function 
`GetPlatformExtensionsString':
src/interface_util/platform.c:7: warning: function 
declaration isn't a prototype
ar -cr build/temp.cygwin-1.3.5-i686-
2.1/libinterface_util.a build/temp.cygwin-1.3.5-i686-
2.1/interface_util.o build/temp.cygwin-1.3.5-i686-
2.1/platform.o
running build_ext
building 'GL.ARB.matrix_palette' extension
error: file 'src/interface/GL.ARB.matrix_palette.c' 
does not exist

any suggestions?

thanks in advance...

-JT


----------------------------------------------------------------------

>Comment By: John A. Turner (turner)
Date: 2001-11-28 13:17

Message:
Logged In: YES 
user_id=20477

gack - sorry

ok, got and built 1.3a5 - now gcc is horking:

gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1/Numeric -
I/usr/include/python2.1 -c 
src/interface/GL.ARB.multitexture.c -o build/temp.cygwin-
1.3.5-i686-2.1/GL.ARB.multitexture.o
In file included from src/interface/GL.ARB.multitexture.c:8:
src/interface/GL.ARB.multitexture.0101.inc: In function 
`SWIG_UnpackData':
src/interface/GL.ARB.multitexture.0101.inc:338: warning: 
`uu' might be used uninitialized in this function
src/interface/GL.ARB.multitexture.0101.inc: In function 
`SWIG_ConvertPtr':
src/interface/GL.ARB.multitexture.0101.inc:404: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc:407: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc:413: warning: 
suggest explicit braces to avoid ambiguous `else'
src/interface/GL.ARB.multitexture.0101.inc: At top level:
src/interface/GL.ARB.multitexture.0101.inc:700: warning: 
function declaration isn't a prototype
src/interface/GL.ARB.multitexture.0101.inc:748: warning: 
function declaration isn't a prototype
gcc: Internal compiler error: program cc1 got fatal signal 
11
error: command 'gcc' failed with exit status 1

this is cygwin 1.3.5 with gcc 2.95.3-5 - should I try
building gcc 3.0.2 or a snapshot or something?



----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-28 06:09

Message:
Logged In: YES 
user_id=21784

As I said in my previous comments, You need SWIG 1.3a5.  
SWIG 1.3.9 won't work.

----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-27 22:39

Message:
Logged In: YES 
user_id=20477

ok, went ahead and grabbed SWIG 1.3.9 and built (no probs),
then cvs-upped PyOpenGL2 and tried again

this time it choked here:

Building wrappers for GL.__init__
Generating shadow version selector
Generating C version selector
Generating wrappers for API version 0x0101
swig -python -Iinterface -shadow -DAPI_VERSION=257 -o 
src/interface/GL.__init___.0101.inc interface/GL/__init__.i
Syntax error
interface/GL/__init__.i:1006. Syntax error in input.


----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-23 08:10

Message:
Logged In: YES 
user_id=21784

You need SWIG 1.3a5 to build out of CVS.  The "cc" problem 
has been fixed in CVS, but the build still doesn't complete 
on my system due to an internal compiler error.  Before you 
do a CVS checkout be sure to move your cygwin.cfg file out 
of the way, since there is one in CVS now.

There is also a complete source code dist (no need for 
SWIG) at http://pyopengl.sf.net/ftp/PyOpenGL-
2.0.1.46.a1.tar.gz


----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-23 00:29

Message:
Logged In: YES 
user_id=20477

ugh - sorry about the formatting of the report - hope it
is understandable - if not let me know and I'll upload files
with the requisite info...


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

[PyOpenGL-Users] [ pyopengl-Support Requests-484774 ] cygwin build problems

[<no...@so...>]

Support Requests item #484774, was opened at 2001-11-23 00:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

Category: build
Group: v2.0
Status: Open
Priority: 5
Submitted By: John A. Turner (turner)
Assigned to: Tarn Weisner Burton (twburton)
Summary: cygwin build problems

Initial Comment:
thought I'd try PyOpenGL2 on win2k/cygwin

using cygwin 1.3.5 and the cygwin port of python 2.1.1
and a fresh CVS checkout of PyOpenGL2

first copied config/win32.cfg to config/cygwin.cfg,
since OpenGL progs compiled with cygwin's gcc use the
normal win32 libs (opengl32, glu32, etc.)

here's what the first bit of setup reports:

PyOpenGL 2.0.1.45.a1 setup

System configuration:
    Platform    = cygwin
    GL Platform = WGL
    Numeric     = 20.2.2
    Build Togl  = yes

1. first prob was that I didn't have SWIG, so I got:

swig -version
unable to execute swig: No such file or directory
swig1.3 -version
unable to execute swig1.3: No such file or directory
warning: build_w: Can't find SWIG, will just have to 
do with the existing wrapper source.

which would likely be ok except that soon after:

cc -I/usr/include/python2.1/Numeric -c _configtest.c -
o _configtest.o
unable to execute cc: No such file or directory

I didn't know how to force setup to use gcc rather than
cc, so I took the easy way out and copied
/usr/bin/gcc.exe to /usr/bin/cc.exe

that at least allowed things to progress...

2. next, saw lots of warnings about missing __init.py__
files, most in the Demo subdir

3. finally, failed with:

running build_clib
building 'interface_util' library
creating build/temp.cygwin-1.3.5-i686-2.1
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/interface_util.c -o 
build/temp.cygwin-1.3.5-i686-2.1/interface_util.o
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsFloatArray':
src/interface_util/interface_util.c:698: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsDoubleArray':
src/interface_util/interface_util.c:701: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsCharArray':
src/interface_util/interface_util.c:704: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedCharArray':
src/interface_util/interface_util.c:707: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsShortArray':
src/interface_util/interface_util.c:710: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedShortArray':
src/interface_util/interface_util.c:713: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsIntArray':
src/interface_util/interface_util.c:716: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedIntArray':
src/interface_util/interface_util.c:719: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: At top level:
src/interface_util/interface_util.c:780: warning: 
function declaration isn't a prototype
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/platform.c -o build/temp.cygwin-
1.3.5-i686-2.1/platform.o
src/interface_util/platform.c:4: warning: function 
declaration isn't a prototype
src/interface_util/platform.c: In function 
`GetPlatformExtensionsString':
src/interface_util/platform.c:7: warning: function 
declaration isn't a prototype
ar -cr build/temp.cygwin-1.3.5-i686-
2.1/libinterface_util.a build/temp.cygwin-1.3.5-i686-
2.1/interface_util.o build/temp.cygwin-1.3.5-i686-
2.1/platform.o
running build_ext
building 'GL.ARB.matrix_palette' extension
error: file 'src/interface/GL.ARB.matrix_palette.c' 
does not exist

any suggestions?

thanks in advance...

-JT


----------------------------------------------------------------------

>Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-28 06:09

Message:
Logged In: YES 
user_id=21784

As I said in my previous comments, You need SWIG 1.3a5.  
SWIG 1.3.9 won't work.

----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-27 22:39

Message:
Logged In: YES 
user_id=20477

ok, went ahead and grabbed SWIG 1.3.9 and built (no probs),
then cvs-upped PyOpenGL2 and tried again

this time it choked here:

Building wrappers for GL.__init__
Generating shadow version selector
Generating C version selector
Generating wrappers for API version 0x0101
swig -python -Iinterface -shadow -DAPI_VERSION=257 -o 
src/interface/GL.__init___.0101.inc interface/GL/__init__.i
Syntax error
interface/GL/__init__.i:1006. Syntax error in input.


----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-23 08:10

Message:
Logged In: YES 
user_id=21784

You need SWIG 1.3a5 to build out of CVS.  The "cc" problem 
has been fixed in CVS, but the build still doesn't complete 
on my system due to an internal compiler error.  Before you 
do a CVS checkout be sure to move your cygwin.cfg file out 
of the way, since there is one in CVS now.

There is also a complete source code dist (no need for 
SWIG) at http://pyopengl.sf.net/ftp/PyOpenGL-
2.0.1.46.a1.tar.gz


----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-23 00:29

Message:
Logged In: YES 
user_id=20477

ugh - sorry about the formatting of the report - hope it
is understandable - if not let me know and I'll upload files
with the requisite info...


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

[PyOpenGL-Users] [ pyopengl-Support Requests-484774 ] cygwin build problems

[<no...@so...>]

Support Requests item #484774, was opened at 2001-11-23 00:26
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988

Category: build
Group: v2.0
Status: Open
Priority: 5
Submitted By: John A. Turner (turner)
Assigned to: Tarn Weisner Burton (twburton)
Summary: cygwin build problems

Initial Comment:
thought I'd try PyOpenGL2 on win2k/cygwin

using cygwin 1.3.5 and the cygwin port of python 2.1.1
and a fresh CVS checkout of PyOpenGL2

first copied config/win32.cfg to config/cygwin.cfg,
since OpenGL progs compiled with cygwin's gcc use the
normal win32 libs (opengl32, glu32, etc.)

here's what the first bit of setup reports:

PyOpenGL 2.0.1.45.a1 setup

System configuration:
    Platform    = cygwin
    GL Platform = WGL
    Numeric     = 20.2.2
    Build Togl  = yes

1. first prob was that I didn't have SWIG, so I got:

swig -version
unable to execute swig: No such file or directory
swig1.3 -version
unable to execute swig1.3: No such file or directory
warning: build_w: Can't find SWIG, will just have to 
do with the existing wrapper source.

which would likely be ok except that soon after:

cc -I/usr/include/python2.1/Numeric -c _configtest.c -
o _configtest.o
unable to execute cc: No such file or directory

I didn't know how to force setup to use gcc rather than
cc, so I took the easy way out and copied
/usr/bin/gcc.exe to /usr/bin/cc.exe

that at least allowed things to progress...

2. next, saw lots of warnings about missing __init.py__
files, most in the Demo subdir

3. finally, failed with:

running build_clib
building 'interface_util' library
creating build/temp.cygwin-1.3.5-i686-2.1
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/interface_util.c -o 
build/temp.cygwin-1.3.5-i686-2.1/interface_util.o
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsFloatArray':
src/interface_util/interface_util.c:698: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsDoubleArray':
src/interface_util/interface_util.c:701: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsCharArray':
src/interface_util/interface_util.c:704: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedCharArray':
src/interface_util/interface_util.c:707: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsShortArray':
src/interface_util/interface_util.c:710: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedShortArray':
src/interface_util/interface_util.c:713: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsIntArray':
src/interface_util/interface_util.c:716: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: In function 
`NonNumeric_PyObject_AsUnsignedIntArray':
src/interface_util/interface_util.c:719: warning: 
suggest parentheses around assignment used as truth 
value
src/interface_util/interface_util.c: At top level:
src/interface_util/interface_util.c:780: warning: 
function declaration isn't a prototype
gcc -g -O2 -Wall -Wstrict-prototypes -DUSE_DL_IMPORT -
DWGL_PLATFORM -DNUMERIC -I/usr/include/python2.1 -
I/usr/include/python2.1/Numeric -
I/usr/include/python2.1/Numeric -c 
src/interface_util/platform.c -o build/temp.cygwin-
1.3.5-i686-2.1/platform.o
src/interface_util/platform.c:4: warning: function 
declaration isn't a prototype
src/interface_util/platform.c: In function 
`GetPlatformExtensionsString':
src/interface_util/platform.c:7: warning: function 
declaration isn't a prototype
ar -cr build/temp.cygwin-1.3.5-i686-
2.1/libinterface_util.a build/temp.cygwin-1.3.5-i686-
2.1/interface_util.o build/temp.cygwin-1.3.5-i686-
2.1/platform.o
running build_ext
building 'GL.ARB.matrix_palette' extension
error: file 'src/interface/GL.ARB.matrix_palette.c' 
does not exist

any suggestions?

thanks in advance...

-JT


----------------------------------------------------------------------

>Comment By: John A. Turner (turner)
Date: 2001-11-27 22:39

Message:
Logged In: YES 
user_id=20477

ok, went ahead and grabbed SWIG 1.3.9 and built (no probs),
then cvs-upped PyOpenGL2 and tried again

this time it choked here:

Building wrappers for GL.__init__
Generating shadow version selector
Generating C version selector
Generating wrappers for API version 0x0101
swig -python -Iinterface -shadow -DAPI_VERSION=257 -o 
src/interface/GL.__init___.0101.inc interface/GL/__init__.i
Syntax error
interface/GL/__init__.i:1006. Syntax error in input.


----------------------------------------------------------------------

Comment By: Tarn Weisner Burton (twburton)
Date: 2001-11-23 08:10

Message:
Logged In: YES 
user_id=21784

You need SWIG 1.3a5 to build out of CVS.  The "cc" problem 
has been fixed in CVS, but the build still doesn't complete 
on my system due to an internal compiler error.  Before you 
do a CVS checkout be sure to move your cygwin.cfg file out 
of the way, since there is one in CVS now.

There is also a complete source code dist (no need for 
SWIG) at http://pyopengl.sf.net/ftp/PyOpenGL-
2.0.1.46.a1.tar.gz


----------------------------------------------------------------------

Comment By: John A. Turner (turner)
Date: 2001-11-23 00:29

Message:
Logged In: YES 
user_id=20477

ugh - sorry about the formatting of the report - hope it
is understandable - if not let me know and I'll upload files
with the requisite info...


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=205988&aid=484774&group_id=5988