Re: Overwriting nativewindow.ws.name to force x11 on R-Pi resuls in UnsatisfiedLinkError
Posted by Sven Gothel on Jun 16, 2015; 5:40am
URL: https://forum.jogamp.org/Overwriting-nativewindow-ws-name-to-force-x11-on-R-Pi-resuls-in-UnsatisfiedLinkError-tp4034695p4034707.html
On 06/16/2015 12:05 AM, gohai [via jogamp] wrote:
> Thanks for your message! I am indeed trying Eric Anholt's vc4 driver. I
> followed his suggestion to compile & install the various packages needed in
> /usr/local, so that I can from the command line either boot the (legacy)
> Raspbian X Server, or the one with Glamour and VC4 - very convenient for
> testing purposes!
>
> That's why I thought that setting "nativewindow.ws.name" to
> "jogamp.newt.driver.x11" would be sufficient to disable the Pi auto-detection.
> But it appears it is not..
>
> Would you consider a (tested) patch that makes it so that any (set) property
> of "nativewindow.ws.name" by the user overrules the auto-detection in
> NativeWindowFactory.java?For the Rasp-Pi WS mode, we shall use nativeWindowingType
instead of nativeWindowingTypePure, allowing to use X11/GL.
Great finding.
-> Bug report -> git patch [and test if possible] -> merge
Thank you!
> (basically using nativewindow.ws.name also for
> nativeWindowingTypePure, if set)
That not.
~Sven
URL: https://forum.jogamp.org/Overwriting-nativewindow-ws-name-to-force-x11-on-R-Pi-resuls-in-UnsatisfiedLinkError-tp4034695p4034707.html
On 06/16/2015 12:05 AM, gohai [via jogamp] wrote:
> Thanks for your message! I am indeed trying Eric Anholt's vc4 driver. I
> followed his suggestion to compile & install the various packages needed in
> /usr/local, so that I can from the command line either boot the (legacy)
> Raspbian X Server, or the one with Glamour and VC4 - very convenient for
> testing purposes!
>
> That's why I thought that setting "nativewindow.ws.name" to
> "jogamp.newt.driver.x11" would be sufficient to disable the Pi auto-detection.
> But it appears it is not..
>
> Would you consider a (tested) patch that makes it so that any (set) property
> of "nativewindow.ws.name" by the user overrules the auto-detection in
> NativeWindowFactory.java?
Great finding.
-> Bug report -> git patch [and test if possible] -> merge
Thank you!
> (basically using nativewindow.ws.name also for
> nativeWindowingTypePure, if set)
That not.
~Sven
signature.asc (828 bytes) | Free forum by Nabble | Edit this page |