I thought it should be easy, but ... geesh! The provider gave me a fairly simple demo program designed to demonstrate some trivial animations. The target platform is an embedded system (MX51) with accelerated support for OpenGL ES 2.0 / OpenVG and EGL.
Unfortunately, the demo also causes an annoying dependency on several useful Qt classes (e.g. QImage). If not for this dependency, I would compile / run the thing on target. But I don't like the idea of โโcross-compiling Qt just to run this little demo - even if there was enough space on the built-in board.
I was hoping that I could run the application on the standard (ish) Ubuntu 10.04 VM and started after these directions to make this happen. And in fact, I managed - for example, after 10 hours - to compile everything and get the binary executable file of the demo program. However, when I run it, I see the following error:
eglCreateWindowSurface: egl error "EGL_BAD_CONFIG" (0x3005)
Sigh. Not what I wanted to see after all these efforts. It seems more complicated than it should be.
Is the built-in GL landscape really such a ghetto that I have to run even trivial programs on the target computer using the vendor-supplied BSP? Judging by the lack of answers to this guy's question , I think the answer may be yes. But I don't even care about acceleration (yet). I just want to run the stupidest OpenGL ES 2 / OpenVG programs on my desktop PC and get an idea of โโhow it looks. (I donโt care if Linux or Windows works on my computer.) How do people do such things?
opengl-es
evadeflow
source share