Skip to content
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 #1618

Open
midwan opened this issue Jan 29, 2025 · 5 comments
Open

Upgrade to SDL3 #1618

midwan opened this issue Jan 29, 2025 · 5 comments
Assignees
Milestone

Comments

@midwan
Copy link
Collaborator

midwan commented Jan 29, 2025

Now that SDL3 is released, it should be tested to see how well things work with it.
The migration guide is here: https://github.com/libsdl-org/SDL/blob/main/docs/README-migration.md

SDL3 releases: https://github.com/libsdl-org/SDL/releases

This should be done in a separate, test branch. I suspect it will take quite a while before everything is migrated properly and we will need time for testing things.

Check if all supported platforms have SDL3 available.

@midwan midwan self-assigned this Jan 29, 2025
@midwan midwan added this to the SDL3 milestone Jan 29, 2025
@midwan midwan changed the title Uprgade to SDL3 Upgrade to SDL3 Jan 29, 2025
@giantclambake
Copy link

giantclambake commented Jan 30, 2025

Man, that's quite the API change ~ having moved this box to debian testing (trixie), I see libsdl3-0 (-dev) are available targets, so that probably infers adoption in debian next at a guess...

...just ftr, there's enough different between bookworm and trixie, that I use a different box for testing amiberry against debian bookworm, so once you spin-up a separate branch, it's easy enough for me to test things ;)

Current state of play ... https://packages.debian.org/search?searchon=sourcenames&keywords=libsdl3

HTH

@agreppin
Copy link

agreppin commented Feb 1, 2025

I tested a build with sdl2-compat and got an assert in a mutex. Seems a work in progress worth to be checked again later.

@midwan
Copy link
Collaborator Author

midwan commented Feb 2, 2025

Well, this issue is about moving the code to use SDL3 directly, not through a compatibility layer. It's a long-term project, since it will take a while to do so, and we'll probably have to keep SDL2 around for a while longer as well (at least until SDL3 is available everywhere, not sure if it's in the older distros).

@ut316ab
Copy link

ut316ab commented Feb 4, 2025

I tested a build with sdl2-compat and got an assert in a mutex. Seems a work in progress worth to be checked again later.

What version of sdl2-compat? If it's the same issue I ran into it was fixed in the newest versions of sdl2-compat and SDL3 see libsdl-org/sdl2-compat#264

However, this does go to show, that taking some time before adopting SDL3 might be beneficial.

@agreppin
Copy link

agreppin commented Feb 4, 2025

@ut316ab sdl2-compat commit 922171f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants