Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs
Date: Thu, 25 Sep 2003 13:06:20 -0500 (CDT)
From: Brian Ford <ford AT vss DOT fsi DOT com>
X-X-Sender: ford AT eos
To: cygwin AT cygwin DOT com
Subject: OpenGL ? Re: gcc 3.3.1: include problem solved
Message-ID: <Pine.GSO.4.56.0309251251530.284@eos>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

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.

What are the long term plans, if any, for reconciling these two
implementations?  It seems silly to have two copies of esstially the same
thing.

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.

Are there any plans to update Cygwin's glut to the current Nate Robins
version?

Thanks.

BTW, I'm more than willing to help here.  But since your the maintainer, I
need to know how you want to proceed.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444

--
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/