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.

SDL 3 support #1736

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions