From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Andre Bleau <bleau@igb.umontreal.ca>
Cc: cygwin@cygwin.com
Subject: Re: Future of OpenGL package (Earnie, please read this)
Date: Fri, 26 Sep 2003 22:57:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.56.0309261843160.3193@slinky.cs.nyu.edu> (raw)
In-Reply-To: <5.2.0.9.0.20030926161937.02cb5af8@irispavp.igb.umontreal.ca>
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 not provide access to OpenGL 1.2+
> > >functionnality. You will still have to program the loading of OpenGL
> > >extensions, if they are available from the graphic card driver. Maybe
> > >something like extgl
> > >(<http://www.levp.de/3d/index.html>http://www.levp.de/3d/index.html)
> > >could be packaged
> > >for Cygwin to make that easier.
> >
> >Sure, I know headers don't magically create functionality. They just
> >allow access to that which already exists. But, most vendors these days
> >(ATI & Nvidia) provide 1.3 or 1.4 functionality. It would be nice to use
> >it without jumping through hoops.
>
> 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.
André,
Cygwin DLL uses the autoload functionality for some of the required
functions, so that they can simply be called after a test (i.e., something
like
if (hasSomeFunction())
callSomeFunction();
Perhaps this could be employed in the OpenGL library layer as well... I
don't know enough off-hand about the autoloading process, but there is a
fairly detailed description in winsup/cygwin/how-autoload-works.txt in the
Cygwin sources. Might be worth investigating...
> [snip]
>
> I think we waited long enough for freeglut and some update of GLUT and GLUI
> is overdue.
>
> So, I propose to make a quick update of the OpenGL package ASAP, while we
> wait for freeglut. To quick update would:
>
> - Remove /usr/include/GL and rely on /usr/include/w32api/GL from the w32api
> package, that would be set as requesite
> - Add glut.h to /usr/include/w32api/GL
So you need to coordinate with Earnie on this (as the subject says).
> - Update the GLUT dll to Nate Robin's 3.7.6
> - Have GLUI and GLUIX libs compiled for gcc 3.3
You will probably also need to release the old libraries as compatibility
packages for those who still use the pre-gcc-3.3 OpenGL binaries.
> - Move the doc to /usr/share/doc
This would be useful.
Just my 2c.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-09-26 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 21:06 Andre Bleau
2003-09-26 22:57 ` Igor Pechtchanski [this message]
2003-10-03 9:11 ` Nigel Stewart and Fiona Smith
2003-09-26 23:19 Brian Ford
[not found] <5.2.0.9.0.20030930190738.02935508@irispavp.igb.umontreal.ca>
2003-10-01 0:56 ` Igor Pechtchanski
2003-10-01 16:04 Brian Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.56.0309261843160.3193@slinky.cs.nyu.edu \
--to=pechtcha@cs.nyu.edu \
--cc=bleau@igb.umontreal.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).