You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is (will) really far future and I do not know whether it is suitable for this library (I mention mainly therefore, it is interesting option to progress of graphic), people of library ebiten found way how remove cgo from MacOs(they are creating own "dlopen" "extension"): hajimehoshi/ebiten#2091, ebitengine/purego#1. It depend on shared library, which open with their own (pure go) "dlopen" and "dlsym", It has advantage at build it is not nessery CGO, on the other hand it has disadvantage too, it need shared library at runtime, so I do not know ..., if yes, it will be very far future
The text was updated successfully, but these errors were encountered:
I have used purego by embedding the shared library in the Go binary and writing the library to a temp directory before dlopen-ing it. I have only done this in Linux with an .so file, so I don't know if macOS security would prevent it.
Of course if we can / should then perhaps a new issue to track that would make sense?
Originally posted by @andydotxyz in #911 (comment)
it is (will) really far future and I do not know whether it is suitable for this library (I mention mainly therefore, it is interesting option to progress of graphic), people of library ebiten found way how remove cgo from MacOs(they are creating own "dlopen" "extension"): hajimehoshi/ebiten#2091, ebitengine/purego#1.
It depend on shared library, which open with their own (pure go) "dlopen" and "dlsym", It has advantage at build it is not nessery CGO, on the other hand it has disadvantage too, it need shared library at runtime, so I do not know ..., if yes, it will be very far future
The text was updated successfully, but these errors were encountered: