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 Message-ID: <1111477463.423fccd741621@webmail.stanford.edu> Date: Mon, 21 Mar 2005 23:44:23 -0800 From: Ajay Jayant Joshi To: cygwin AT cygwin DOT com Subject: Cygwin and ARB shader MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.7 X-Authenticated-User: joshi83 Hi Is it possible to use ARB extensions (shaders) under cygwin? I am not able to use glGenProgramsARB_t() --------------------------------------------------------------- // Generate a valid program ID // m_program_id => GLuint m_program_id ; glGenProgramsARB_t(1, &m_program_id); assert(m_program_id); // typedef void (APIENTRY * glGenProgramsARB_t) (GLsizein, GLuint*); --------------------------------------------------------------- This assertion fails. I am using same code under Linux and it works fine. Under Linux I am using: -- ATI FireGL (256MB) card -- fglrx drivers -- ARB vertex and fragment shaders I am using same card and same shaders on windows (cygwin). And have installed latest Fire X series drivers for XP from ATI. Do i need to install any drivers in cygwin? ( i am using "/lib/w32api/libopengl32.a" as libGL.a (sym link) ) glxinfo on Linux shows : Direct Rendering : YES OpenGL Drivers: ATI glxinfo on Windows (Cygwin) shows: Direct Rendering : NO OpenGL Drivers: MESA Can that be a problem? (When latest drivers were not installed on Linux i got exactly same assertion failure and when i used new drivers everything was ok.) How do we make cygwin aware of underlying ATI card? Is direct rendering equivalent to using vertext/fragment shaders ? (i.e. do I need direct rendering=YES for using ARB shaders ? ) Thanks a lot for your time, Regards Ajay Joshi -- 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/