maemo.org - Talk - near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

maemo.org - Talk (https://talk.maemo.org/index.php)

- General (https://talk.maemo.org/forumdisplay.php?f=7)

- - near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1 (https://talk.maemo.org/showthread.php?t=84993)

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

OMG. I still have to "cope with" (=fight against) historically grown usage of CVS weekly. The same with EMACS (seriously guys, how can anyone be using it as a mailreader/PIM suite etc too?), procmail (which is ok but cumbersome) and (albeit to a lesser degree) SVN (which tends to corrupt repositories if used multi-site).

I'm ok with makefiles, they are simple and clean. And when you lose the oversight/control of your build processes and the output seems a bit unpredictable, it doesn't matter what solution one uses anyway. But ant is a nice build environment too, hmm...

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

so any autofool here to fix this configure ? I am too bored to do it myself :)

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

I am going to experiment with this. Let's see if I can use this to build Blender with OpenGL acceleration! (I know someone did three years ago or so, but the code never appeared.)

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

Is it possible to get OpenGL support by compiling MesaLib with --enable-gles1 and --enable-gles2 flags? I've compiled MesaLib 7.11.2 with these flags, on device with tanners gcc4-4.

Output from ./configure --enable-gles1 --enable-gles2

Code:

OpenGL: yes (ES1: yes ES2: yes)

Output from glxgears:

Code:

Nokia-N900-40-4_PR_001:~/build/glx$ ./glxgears 

109 frames in 5.0 seconds = 21.714 FPS

158 frames in 5.0 seconds = 31.515 FPS

155 frames in 5.0 seconds = 30.957 FPS

* Window needs to be fullscreen to actually see the gears
rootsh wmctrl -i -r $(wmctrl -l | grep 'glxgears' | awk '{print $1}') -b add,fullscreen

Code:

Nokia-N900-40-4_PR_001:~/build/glx$ ./glxinfo | grep rende

direct rendering: Yes

OpenGL renderer string: Mesa X11

Full output of glxinfo -v
http://pastebin.com/YXuvYVCN

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

Is it possible to use OpenGL by compiling MesaLib with --enable-gles1 and --enable-gles 2 flags? I've compiled MesaLib on device with these flags using Tanners gcc4.4

Output from ./configure --enable-gles1 --enable-gles2

Code:

OpenGL: yes (ES1: yes ES2: yes)

Output from ./glxgears

Code:

Nokia-N900-40-4_PR_001:~/build/glx$ ./glxgears 

86 frames in 5.0 seconds = 17.117 FPS

158 frames in 5.0 seconds = 31.400 FPS

155 frames in 5.0 seconds = 30.947 FPS

159 frames in 5.0 seconds = 31.672 FPS

Nokia-N900-40-4_PR_001:~/build/glx$

*to actually see the gears, the window needs to be fullscreen
rootsh wmctrl -i -r $(wmctrl -l | grep 'glxgears' | awk '{print $1}') -b add,fullscreen

Output from glxinfo | grep rende

Code:

direct rendering: Yes

OpenGL renderer string: Mesa X11

Full output from glxinfo -v
http://pastebin.com/0hrpPSxD

edit: output from glew-utils

visualinfo

Code:

OpenGL vendor string: Brian Paul

OpenGL renderer string: Mesa X11

OpenGL version string: 2.1 Mesa 7.11.2

OpenGL extensions (GL_):

http://pastebin.com/wA3NHP3J

glewinfo

Code:

---------------------------

    GLEW Extension Info

---------------------------



GLEW version 1.5.8

Reporting capabilities of display :0.0, visual 0x21

Running on a Mesa X11 from Brian Paul

OpenGL version 2.1 Mesa 7.11.2 is supported

http://pastebin.com/TRScasUs

Re: near-complete OpenGL 1.3 API implemented using OpenGL ES 1.1

taixzo: It will be amzing to have it on a mobile device. Good luck!