OpenGL ES 2.0 Coming to a Desktop Near You
The Khronos Group developed OpenGL ES 2.0 to help bring modern graphics capabilities to mobile platforms. This API has been adopted by many embedded devices such as consoles, mobile phones, handheld computers, and vehicles. As a subset of the full OpenGL 2.0 specification, OpenGL ES 2.0 limits the embedded graphics API to only the most common functionality, reducing the implementation burden for embedded hardware.
The Khronos WebGL working group is developing a 3D API for the web, bringing 3D content right to the web browser using open standards. This effort uses an OpenGL ES 2.0-like interface as its backbone. OpenGL ES 2.0 was chosen as a common denominator of 3D acceleration on devices supporting web browsers.
AMD has just announced support for OpenGL ES on desktop platforms. This means ATI Radeon™, ATI Mobility Radeon™, ATI FirePro™ and ATI FireGL™ graphics cards released since 2008 will run OpenGL ES 2.0 natively. No longer do embedded developers need to exclusively use emulators or translation layers to get OpenGL ES 2.0 code up and running. Development can be done on a more accessible desktop system on either Microsoft Win7, Vista, or XP with ATI Catalyst™ software 10.8 or newer. Support for Linux is planned to follow with ATI Catalyst™ 10.9 software.
Accessing OpenGL ES 2.0 on the desktop is very similar to traditional embedded systems and can be done by using the EGL window management system. AMD has provided a simple sample app available here (updated code 1/31/12) to help developers get started using OpenGL ES on the desktop. Give OpenGL ES 2.0 a try today and let us know what you think!
Nick Haemel is a Software Development Engineer on the AMD OpenGL team. His postings are his own opinions and may not represent AMD’s positions, strategies or opinions. Links to third party sites are provided for convenience and unless explicitly stated, AMD is not responsible for the contents of such linked sites and no endorsement is implied.
POSTED IN: Inside Dev Central
TAGS: ATI FireGL, ATI FirePro, ATI Radeon, embedded, OpenGL
SHARE:
COMMENTS: 19
No one answer~? There seems to be a bug in the example.
Could you please reply to me about the sample? I compiled the sample. And I found that the PROC is invoked in WM_SIZE before the PROC is imported. So it reports error. Is the sample tested before release? So I’d like to know whether this is problem of my computer or the sample. Appreciate for your reply.
Does replying my comments cost too much your time? You released the example. And I compile on my computer. It reports that the GL PROC is invoked in WM_SIZE before the PROC is imported. Could you please check it out to let me know whether it’s my fault or your mistake in your example? Or this is the attitude AMD takes to treat the developers? No wonder Intel will take more users & developers.
תיקון פייסבוק opwngl es 2.0 comins to a desktop
near you
There does appear to be a problem with the sample. You are right that the resize event handler is being invoked prior to the entry points being loaded. We will rectify the sample.
Kishore Mulchandani
There seems to be a bug in the example.
http://www.miumius.com