I think we waited long enough for freeglut and some update of GLUT and
GLUI is overdue.
FreeGLUT has certainly gained momentum in recent months,
but I sould say that GLUT will still be needed for a
while. I recently suggested to the FreeGLUT list that
GL/freeglut.h sho
Andre Bleau wrote:
>Igor Pechtchanski wrote:
>
>>Andre Bleau wrote:
>>
>>>Even, with 1.4 headers, you would sill need to jump through hoops to use
>>>1.4 functionality. You will still need to load the functions dynamicaly
>>>before using them. You wouldn't be able to simply call the functions as
>
Andre Bleau wrote:
>Brian Ford wrote:
>
>>Andre Bleau wrote:
>>
>>>Brian Ford wrote:
>>>
>
>1.2 and 1.3 defines & prototypes are already there in
>/usr/include/w32api/GL/glext.h
>
Yes, I know. That statement started this thread.
They (1.3+) are not available in /usr/include/GL/gl.h which is now
On Tue, 30 Sep 2003, Andre Bleau wrote:
> Igor Pechtchanski wrote:
>
> >On Fri, 26 Sep 2003, Andre Bleau wrote:
> >
> > > ...
> > > Even, with 1.4 headers, you would sill need to jump through hoops to use
> > > 1.4 functionality. You will still need to load the functions dynamicaly
> > > before us
Igor Pechtchanski wrote:
On Fri, 26 Sep 2003, Andre Bleau wrote:
> ...
> Even, with 1.4 headers, you would sill need to jump through hoops to use
> 1.4 functionality. You will still need to load the functions dynamicaly
> before using them. You wouldn't be able to simply call the functions as
> w
Brian Ford wrote:
...
>Even, with 1.4 headers, you would sill need to jump through hoops to use
>1.4 functionality. You will still need to load the functions dynamicaly
>before using them. You wouldn't be able to simply call the functions as
>when developing for UNIX.
>
A lot of the functionallity
Andre Bleau wrote:
>Brian Ford wrote:
>
>No; if /usr/include/GL does not exist anymore, gcc will look in
>/usr/include/w32api/GL for #include directives.
>
Ahh..., ok. I didn't realize that. Makes sense, though. I was just
being dense.
>Even, with 1.4 headers, you would sill need to jump thro
On Fri, 26 Sep 2003, Andre Bleau wrote:
> Brian Ford wrote:
>
> >Andre Bleau wrote:
> >...
> >
> > >>Are there any plans to update Cygwin's OpenGL headers to include 1.3 or
> > >>1.4 support? Be it via using the w32api Mesa ones, or by other means.
> > >
> > >Let that be clear: headers alone will
Brian Ford wrote:
Andre Bleau wrote:
...
>API to native Windows OpenGL implementation, accessible through M$'s
>opengl32.dll could be in the w32api package, as it is now. The GL include
>directory could be in /usr/include/w32api exclusively, without need for
>another in /usr/include.
>
That sounds
Andre Bleau wrote:
>Brian Ford wrote:
>
>>I am glad that the ambiguity in gcc include search paths has been
>>resolved. However, the OpenGL includes in w32api/GL are from Mesa, and
>>are thus more complete and up-to-date.
>
>Well, I hope that Earnie Boyd, maintainer for the w32api package, will
>
Brian Ford wrote:
These questions are mainly directed at Andre Bleau (Cygwin's OpenGL
maintainer).
I am glad that the ambiguity in gcc include search paths has been
resolved. However, the OpenGL includes in w32api/GL are from Mesa, and
are thus more complete and up-to-date.
Well, I hope that Earn
11 matches
Mail list logo
