-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“Illegal reflective access by com.jogamp.common.os.NativeLibrary” when using P3D (caused by JOGL) #22
Comments
Created by: sampottinger This comes from JOGL itself and is related to JEP 261 as tracked at https://jogamp.org/bugzilla//show_bug.cgi?id=1363. There is no resolution on the Processing side except for moving to LWJGL or waiting for an update from JOGL. I believe @codeanticode is looking into LWJGL. |
Created by: codeanticode @sampottinger indeed, I created a fork from your earlier processing-openjdk repo that uses LWJGL for the core OpenGL renderer: https://github.com/codeanticode/processing-openjdk/tree/lwjgl-renderer It still needs some work to encapsulate all AWT dependencies so they are not used when launching a sketch with the P2D or P3D renderers. |
Created by: neilcsmith-net @codeanticode that's not quite correct. There is only a requirement to encapsulate aspects of AWT that can't work headless, is much less. I have a fork of 3.5.3 with minimal changes to work headless with LWJGL already. If there's desire to switch upstream I can open an issue and work on a PR for here or your branch. Mainly a need to push things down into the Surface implementations. And find a way to execute tasks on the main thread. |
Created by: benfry Should be fixed with the JOGL 2.4 RC that's included with 4.0a1. |
Created by: github-actions[bot] This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Created by: sampottinger
Filing for kll from a processing forums discussion. The following happens when using P3D:
The text was updated successfully, but these errors were encountered: