8000 SDL 3 support · Issue #1736 · chocolate-doom/chocolate-doom · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SDL 3 support #1736

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.

Sign up for GitHub

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

Jump to bottom
Open
turol opened this issue Apr 12, 2025 · 2 comments
Open

SDL 3 support #1736

turol opened this issue Apr 12, 2025 · 2 comments
Labels
build feature request good first issue help wanted

Comments

@turol
Copy link
Member
turol commented Apr 12, 2025

SDL 3 has been released. We should add native support for it.

Also it seems that the issue template is broken, I did not get a template when opening this issue.
@rfomin
Copy link
Contributor
rfomin commented Apr 12, 2025

SDL3_Net is not finished yet. And the current development version doesn't have UDP broadcast: libsdl-org/SDL_net#97

@NY00123
Copy link
Contributor
NY00123 commented May 20, 2025

Good to see this has been opened. One question I've had in my mind, is if SDL_Mixer and SDL_Net should still be used as currently done. Migrating to alternatives will indeed require more than little work by anyone interested in doing so, but I'm bringing it as a suggestion for now.

  • From what I recall, it should be possible to replace usage of SDL_Net with direct socket API manipulation on familiar desktop platforms; Winsock and Berkeley sockets are the main APIs I know to be relevant, but maybe not as much on certain newer platforms. The two APIs are not identical, but there should be enough similarities.

  • Of course, if SDL_Net is replaced, more network/multiplayer testing will probably be desired.

  • Regarding SDL_Mixer, more work may be required for removing the dependency on it. From what I may see in the source code, right now, the library may be used for opening music files, either digitized (via music packs) or MIDI. Other functionalities may also need to have replacements implemented, e.g., an alternative to the calls to Mix_RegisterEffect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build feature request good first issue help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@turol @rfomin @NY00123
0