We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v0.8.0-alpha.3
go version
go version go1.22.5 darwin/arm64
Call purego.Dlopen("libGLESv2.so", purego.RTLD_LAZY|purego.RTLD_GLOBAL) on Android
purego.Dlopen("libGLESv2.so", purego.RTLD_LAZY|purego.RTLD_GLOBAL)
An so file is loaded
Error:
invalid flags to dlopen: 101
Galaxy A02s has 32bits Android OS though the CPU is 64bit. Also, Android has different definitions for RTLD_* for 32bits.
RTLD_*
Even though I used C's RTLD_*, another crash happened. I am not sure when this happened. Maybe loading a symbol?
See also hajimehoshi/ebiten#3052
The text was updated successfully, but these errors were encountered:
This is such a strange case where it's a 64Bit CPU but a 32bit OS.
Sorry, something went wrong.
Indeed...
internal/graphicsdriver/opengl/gl: use PureGo version for Android again
2a34d1d
This is basically a revert for 297efea. This updates PureGo for the Android issue. Updates #3052 Updates ebitengine/purego#262
Successfully merging a pull request may close this issue.
PureGo Version
v0.8.0-alpha.3
Operating System
Go Version (
go version
)go version go1.22.5 darwin/arm64
What steps will reproduce the problem?
Call
purego.Dlopen("libGLESv2.so", purego.RTLD_LAZY|purego.RTLD_GLOBAL)
on AndroidWhat is the expected result?
An so file is loaded
What happens instead?
Error:
Anything else you feel useful to add?
Galaxy A02s has 32bits Android OS though the CPU is 64bit. Also, Android has different definitions for
RTLD_*
for 32bits.Even though I used C's
RTLD_*
, another crash happened. I am not sure when this happened. Maybe loading a symbol?See also hajimehoshi/ebiten#3052
The text was updated successfully, but these errors were encountered: