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: Wed, 15 Oct 2003 11:04:35 -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: Re: Cygwin and vertex/pixel programs
In-Reply-To: <Pine.LNX.4.58.0310151133450.1045@apollonius.research.att.com>
Message-ID: <Pine.GSO.4.56.0310151049160.823@eos>
References: <Pine DOT LNX DOT 4 DOT 58 DOT 0310151133450 DOT 1045 AT apollonius DOT research DOT att DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 15 Oct 2003, Suresh Venkatasubramanian wrote:

> i have an nvidia graphics card that doesn't yet have linux drivers.
> hence, I was considering using cygwin to write my code in windows.
>
Really?  I thought that all Nvidia cards capable of pixel/vertex shaders
had Linux driver support.

> Now, from what i understand, cygwin allows me to link to the native
> windows opengl dlls, is that correct?
>
Yes.

> And therefore, does that mean that access to the latest
> opengl dlls is independent of cygwin (i just have to download the latest
> ones) ?
>
I guess so.  This question is not clear.

> The reason this is of concern is because my work typically makes
> use of the newer extensions like vertex programs and fragment programs,
> (the ARB_fragment_program and ARB_vertex_program extensions etc)
> and I would need to be able to use those.
>
They work.

Please see /usr/doc/opengl-1.1.0/README.txt.  Note that some of that info
is out of date.  In particular, if you are using gcc 3.3.1, you will want
to move /usr/include/GL/[gl.h glu.h] out of the way so you get the ones in
/usr/include/w32api/GL instead.  Also, you will need to include GL/glext.h
(which comes from there too), and ignore the references to GL_VERSION_*.

An updated OpenGL package for Cygwin is in the works to fix these issues
(I think).

A second note.  You mentioned Linux, which would imply that you expect to
code using GLX.  Xfree86 under Cygwin does not currently use a pass
through mechanism to the native OpenGL DLLs.  Instead, it uses Mesa
software rendering (not HW accelerated), and the previous
document/comments do not apply.  If you use this method, use standard GLX
includes/libs ie. -I /usr/X11R6/include -L /usr/X11R6/lib -lGLU -lGL.

You must use Windows wgl windowing code (ie. no X) to get acceleration and
native OpenGL DLLs.

HTH, and wasn't too confusing.

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