Posted by Xerxes Rånby on Sep 07, 2016; 10:03am
URL: https://forum.jogamp.org/JOGL-2-0-OpenGL-OpenGL-ES-backend-for-LibGDX-tp4027689p4037104.html

On 9th Feb 2016 Raspbian Raspberry Pi system images started to ship their
system with two incompatible implementations of OpenGL ES drivers installed
at the same time.
https://jogamp.org/bugzilla/show_bug.cgi?id=1290

The Mesa3D OpenGL ES implementation work in combination with AWT and NEWT
GLWindow
The Broadcom OpenGL ES implementation only work in combination with NEWT
GLWindow

Both implementations allow you to run libgdx applications.

The error "undefined symbol: bcm_host_init" is caused by jogamp trying to
initialize and use a function that is only found when using the Broadcom
OpenGL ES driver. However the operating systems dynamic linker have opened
the Mesa3D driver and the Mesa3D driver that cant be initialized the same
way and do not contain the Broadcom specific function.

Raspberry Pi foundation is aware that they currently ship a system where
OpenGL fails initialize if you initialize OpenGL dynamically however there
is no consensus how to resolve the issue because the foundation insists of
having two drivers installed at the same time.
https://github.com/anholt/mesa/issues/24

When using JogAmp 2.3.2 the only known workaround at the moment is to
remove one of the two implementations from the system.

Workaround 1:
To use Mesa3D OpenGL ES implementation you have to first select the
experimental opengl driver in raspi-config
then you have to make the Broadcom driver unavailable by renaming the
/opt/vc driver folder
sudo mv /opt/vc /opt/vc-disabled

Workaround 2:
To get Broadcom OpenGL ES initialization working you uninstall Mesa3d
OpenGL ES
sudo aptitude remove libgles1-mesa libgles2-mesa libgl1-mesa-dri




2016-09-07 11:41 GMT+02:00 gouessej [via jogamp] <
ml-node+s762907n4037102h25@n3.nabble.com>:

> Hi
>
> The .so files must be updated, I'm almost sure of that. Maybe Xerxes can
> help you.
>
> Maybe it's a bit off topic but "I exported the runnable jar of my Desktop
> launcher" is vague, it doesn't tell us exactly which tools you used to do
> so and we don't know if some files are missing.
> Julien Gouesse | Personal blog <http://gouessej.wordpress.com> | Website
> <http://tuer.sourceforge.net> | Follow me on Identi.ca
> <http://identi.ca/gouessej>