Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: Fri, 24 Oct 2003 10:55:01 -0500 (CDT) From: Brian Ford X-X-Sender: ford AT eos To: suresh AT research DOT att DOT com cc: cygwin AT cygwin DOT com Subject: Re: OpenGL and Cygwin In-Reply-To: <200310240357.h9O3v8Z24635@bigmail.research.att.com> Message-ID: References: <200310240357 DOT h9O3v8Z24635 AT bigmail DOT research DOT att DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Oct 2003 suresh AT research DOT att DOT com wrote: > thanks Andre ! the fix worked. I can now compile helloglut and many of > the red book opengl demos. > I went back to review this thread, but I am unsure exactly what fix you actually used. It would help greatly to see your exact compile line, and to know what headers/libs you are, or think you are, using. Did you move /usr/include/GL/[gl.h glu.h] out of the way like I suggested? BTW, Andre Bleau wrote: >Forget about LD_LIBRARY_PATH; it is not used by cygwin. Plain old PATH is sort of the equivalent here to find DLLs. > I noticed that glGetMinmax and some histogram related functions are not > supported. It is possible that this is because these are opengl 1.2 > functions. > I short, yes. But I really need to know what headers/libs you are using to give you the correct advice on how to obtain them. > By setting appropriate flags I got the appropriate GL_flags > set correctly: > You mean defining GL_VERSION_1_2? So, you are using the headers from the opengl package in /usr/include/GL. That is ok as long as you don't want 1.3 functionality. Otherwise, I suggest following my "move out of the way" suggestion. > however it appears that the libopengl32.a supplied with > cygwin is only opengl1.1 compliant, which appears to be consistent with > the README. > That is because Microsoft only supplies 1.1 functionality. If you want greater, you must load those functions as extensions. > I have more recent nvidia drivers (I think :)): Is there any way to > convert them to to a linkable form ? (i.e using dlltool or something like > that). I > You do. Most nvidia drivers are 1.3 or 1.4. You don't need to convert them, they are linkable as is via the normal described methods. I think I can probably be of great help to you here, but you need to describe you problems/goals in much greater detail. I promise to try my best to help if you do. -- 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/