[pygccxml-development] Utilizing typedef in code generated by Py++

[Patrick H. <pa...@in...>]

I have run into a case where a typedef used for portability varies in the=

actual type in use. The type being defined is GLenum from OpenGL. On Linu=
x
and Windows, the underlying type for GLenum is unsigned int, but on Mac O=
S
X, it is unsigned long. When Py++ generates the Boost.Python bindings cod=
e
for functions that include GLenum in their signature, it uses the underly=
ing
type in the function signature typedef rather than GLenum. This results i=
n
compile failures when generating the code on Linux and trying to compile =
on
Mac OS X (or vice versa).

In trying to resolve this, I have come up with two questions:

   1. Can Py++ generate code that uses typedefs instead of fully expanded=

      types?
   2. Is there a way to have a special case where GLenum can be used in t=
he
      generated code and everything else can continue using fully expande=
d
      types?

The second question came to mind because this currently affects only two
=2Ecpp files out of over 350 being generated by Py++.

Thanks in advance.

 -Patrick


--=20
Patrick L. Hartling
VP Engineering, Infiscape Corp.
http://www.infiscape.com/