-
Notifications
You must be signed in to change notification settings - Fork 182
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
Expose glfwGetProcAddress in Context #234
Comments
function pointers and cgo are very messy to implement. what use case do you have for it? |
I have a use case where I need to let a shared library call GetProcAddress. https://github.com/libretro/ludo/pull/91/files#diff-6a7f136db4c2e8bb2b91f3fa3b4079bdR374 This is a C version of this: https://github.com/heuripedes/sdlarch/blob/master/sdlarch.c#L582 |
you can't call the function that you get the adress for though. you need an
intermediary C function where you call it thus it makes more sense to have
specific C functions for the job and wrap them instead of getProcAddress.
…On Wed, 2 Jan 2019, 06:28 Jean-André Santoni ***@***.*** wrote:
I have a use case where I need to let a shared library call
GetProcAddress.
https://github.com/libretro/ludo/pull/91/files#diff-6a7f136db4c2e8bb2b91f3fa3b4079bdR374
This is a C version of this:
https://github.com/heuripedes/sdlarch/blob/master/sdlarch.c#L582
That I'm trying to adapt to go.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#234 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AANq8OfVhnmzb-wnQluOuwrvLf-huPoiks5u_CdWgaJpZM4Zk0vY>
.
|
I need to avoid using glfw functions in my libretro package, because this package is a go binding for a C library and it has to remain agnostic. Some people may want to use it with SDL, some other with pure Windows or Apple rendering libs. |
I believe the Drakirus/go-flutter-desktop-embedder project would benefit from a properly exported The go code over there doesn't need to call the functions that are returned by |
Thanks @tapir |
See https://www.glfw.org/docs/latest/group__context.html#ga35f1837e6f666781842483937612f163
The text was updated successfully, but these errors were encountered: