Silent-Hunter
Hardcore Member
- Joined
- May 29, 2010
- Messages
- 3,485
Perhaps. I looked in CMakeLists.txt, and could not find any mention of GL2
it's not in the "root" one, but should be in the sr/c one or something like that. I'll look at that later.Perhaps. I looked in CMakeLists.txt, and could not find any mention of GL2
pi@raspberrypi ~/glshim $ cmake . -DBCMHOST=1; make GL
-- Configuring done
-- Generating done
-- Build files have been written to: /home/pi/glshim
Scanning dependencies of target GL
[ 4%] Building C object src/CMakeFiles/GL.dir/gl/array.c.o
In file included from /home/pi/glshim/src/gl/array.h:1:0,
from /home/pi/glshim/src/gl/array.c:1:
/home/pi/glshim/src/gl/gl.h:35:93: warning: ‘struct EGLClientPixmapHI’ declared inside parameter list [enabled by default]
/home/pi/glshim/src/gl/gl.h:35:93: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
/home/pi/glshim/src/gl/gl.h:36:23: error: expected declaration specifiers or ‘...’ before ‘*’ token
/home/pi/glshim/src/gl/gl.h:37:23: error: expected declaration specifiers or ‘...’ before ‘*’ token
/home/pi/glshim/src/gl/gl.h:38:95: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:43:63: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:54:37: error: expected declaration specifiers or ‘...’ before ‘*’ token
/home/pi/glshim/src/gl/gl.h:61:61: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:62:65: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:68:62: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:69:71: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:70:81: error: unknown type name ‘EGLStreamKHR’
/home/pi/glshim/src/gl/gl.h:71:71: error: unknown type name ‘EGLStreamKHR’
/opt/vc/include/interface/vcos/vcos_timer.h:112:6: warning: inline function ‘vcos_timer_delete’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:109:6: warning: inline function ‘vcos_timer_reset’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:102:6: warning: inline function ‘vcos_timer_cancel’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:95:6: warning: inline function ‘vcos_timer_set’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:80:15: warning: inline function ‘vcos_timer_create’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:269:6: warning: inline function ‘vcos_thread_resume’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:262:5: warning: inline function ‘vcos_thread_running’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:251:15: warning: inline function ‘vcos_change_preemption’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:234:6: warning: inline function ‘vcos_thread_relinquish’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:186:15: warning: inline function ‘vcos_thread_get_affinity’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:112:6: warning: inline function ‘vcos_timer_delete’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:109:6: warning: inline function ‘vcos_timer_reset’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:102:6: warning: inline function ‘vcos_timer_cancel’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:95:6: warning: inline function ‘vcos_timer_set’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_timer.h:80:15: warning: inline function ‘vcos_timer_create’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:269:6: warning: inline function ‘vcos_thread_resume’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:262:5: warning: inline function ‘vcos_thread_running’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:251:15: warning: inline function ‘vcos_change_preemption’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:234:6: warning: inline function ‘vcos_thread_relinquish’ declared but never defined [enabled by default]
/opt/vc/include/interface/vcos/vcos_thread.h:186:15: warning: inline function ‘vcos_thread_get_affinity’ declared but never defined [enabled by default]
src/CMakeFiles/GL.dir/build.make:54: recipe for target 'src/CMakeFiles/GL.dir/gl/array.c.o' failed
make[3]: *** [src/CMakeFiles/GL.dir/gl/array.c.o] Error 1
CMakeFiles/Makefile2:79: recipe for target 'src/CMakeFiles/GL.dir/all' failed
make[2]: *** [src/CMakeFiles/GL.dir/all] Error 2
CMakeFiles/Makefile2:91: recipe for target 'src/CMakeFiles/GL.dir/rule' failed
make[1]: *** [src/CMakeFiles/GL.dir/rule] Error 2
Makefile:106: recipe for target 'GL' failed
make: *** [GL] Error 2
Potential of 3D acceleration for x86 linux and Windows game via WINE.What does all this mean?
Umm yeah this IS posted in the Pandora section. However there still not an easy install process on the Pandora for Exagear Desktop and there still may be issues with audio.What about Pandora?
Sooo... any chance of trying this out on your OMAP5 board?Umm yeah this IS posted in the Pandora section. However there still not an easy install process on the Pandora for Exagear Desktop and there still may be issues with audio.What about Pandora?
This is all exciting; if you do make a video it would be interesting to see!I've tested this with Stepmania, glxgears, and Unreal Tournament 1. I'll probably do a video tonight, though I need to work on performance a bit.
The current unstable branch of glshim is capable of rendering OpenGL in the public release of Exagear (as well as QEMU).
You'll want to do this over SSH as you might need to hard kill one of the sides when you quit. I'm working on making it more stable.
- On a 32-bit x86 machine, build the unstable glshim branch (`cmake .; make`), then copy lib/libGL.so.1 to /usr/local/lib in your Exagear chroot (somewhere in /opt/exagear/images).
- On your ARM machine, build libgl_remote from the unstable glshim branch (`cmake .; make libgl_remote`), then copy bin/libgl_remote to /usr/local/bin.
- Add libgl_remote to /opt/exagear/images/ubuntu-1204lts/.exagear/opaths-list like this: "/usr/local/bin/libgl_remote=/usr/local/bin/libgl_remote"
3.1. `sudo touch /opt/exagear/images/ubuntu-1204lts/usr/local/bin/libgl_remote`
3.2. Make sure --opaths-list is in your exagear command line (look at the bottom of /usr/bin/exagear).
- Run an OpenGL program in Exagear with environment variables like so: `LIBGL_REMOTE=1 ./path/to/exe`. If it doesn't work on your device, try any combination of LIBGL_FB=1 and LIBGL_X11_REOPEN=1.
I've tested this with Stepmania, glxgears, and Unreal Tournament 1. I'll probably do a video tonight, though I need to work on performance a bit.
Edit: Exagear just got back to me about running native programs, updated the steps. Here are the old steps if you need them:
- Run an OpenGL program in Exagear with environment variables like so: `LIBGL_REMOTE=1 LIBGL_REMOTE_NOSPAWN=1 ./path/to/exe`
- Look in the output for `libGL: shm_name='/glshim.0'`, and copy the `/glshim.0` part.
- On the ARM side, run `libgl_remote /glshim.0`.
Will this accelerate DirectX applications or is the OpenGL 1.x exposed by GLshim not enough for that? If so which DX versions?Potential of 3D acceleration for x86 linux and Windows game via WINE.What does all this mean?
Try the LIBGL_FB=1 environment variable. Also, try running it under gdb so we can see where it segfaults, or use LIBGL_STACKTRACE=1 for the builtin segfault handler.Does anyone have any advice on how to debug this? What are those symbols (glXChooseVisual and glXCreateContext) I'm missing?
LIBGL_FB and LIBGL_STACKTRACE have had no effect. Running under gdb suggests (as per my limited knowlege) that the segfault comes from bcm_host_init():Try the LIBGL_FB=1 environment variable. Also, try running it under gdb so we can see where it segfaults, or use LIBGL_STACKTRACE=1 for the builtin segfault handler.