#Supporting EGL extensions

1 messages · Page 1 of 1 (latest)

upbeat apex
#

Good morning, thank you for the EGL support.
I was wondering what the plan is for the EGL extensions support?
Or should the user code the necessary extension by "c" processes?

Wasn't there a blog discussing about adding foreign C libraries processes yourself? I found the bindings to C blog.

echo bridge
#

Hey, I've added a couple functions to the existing egl bindings, maybe I can help. What are you trying to do exactly?

upbeat apex
#

There was a solution on another thread.

Summary for anyone that runs into this:

  • Get .dlls and .libs from libraries you're wanting to create bindings for
  • Use bindgen to create the bindings but make sure you include the libraries include files in the .sjson config
  • Store the .odin binding files in e.g. vendor/your_library
  • Import the library using the usual Odin style import
  • Ensure the .dlls of the C libraries are in your projects folder
  • Build your .odin program and the bindings should allow you to access the C libraries functions etc
upbeat apex
echo bridge
#

Hasn't bindgen solve this?

upbeat apex
#

Just wanted to let you know, if you had some other solutions for this. Better to look what alternatives there are or should people stick with one solution per problem.