-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
Upgrade to SDL3 #618
Comments
Hi @lukewilson2002, thank you for asking! There's no plan yet to update the project to SDL3 due to limited resources 💦 but I'm considering setting up dedicated directory if we do plan on implementing it and perhaps eventually restructuring and renaming the project to go-sdl. |
Hey @veeableful , I created a PoC if someone is interested: flibitijibibo uses c2ffi to create a json of the SDL3 API: https://github.com/flibitijibibo/SDL3-CS/blob/main/GenerateBindings/assets/ffi.json With the help of that json and the go source code generator jennifer https://github.com/dave/jennifer, it should be possible to auto-generate the bindings (or at least a nasty part). |
That is amazing @JupiterRider! I was able to build on macOS and cross-compile to Linux and they both seem to run without issues after installing SDL3 and making sure the libraries can be looked up. I'm unfamiliar with the tools used. Would it enable mass renames on functions and variables as well? If so, I think that's a great approach moving forward. Please let me know if you would like me to point users to your project for SDL3 or do something else! |
I think a new repository makes sense, because SDL3 and removing cgo is a breaking change. Of course, if you don't want to host the new repository, you can point users to mine. |
Thank you @JupiterRider! I have updated the README to refer users to the repository for SDL3. |
SDL3 released on Jan 21. Are there any plans to upgrade this project, and how would that be done with the current name? Would there be a new repository go-sdl3?
https://github.com/libsdl-org/SDL/releases/tag/release-3.2.0
The text was updated successfully, but these errors were encountered: