version constraint on SDL2 will not accept future releases

[Simon McVittie]

The SDL maintainers are planning to switch its versioning scheme to look more like GTK's, making use of the minor version to indicate feature releases with backwards-compatible changes. See ​https://github.com/libsdl-org/SDL/blob/main/docs/README-versions.md for the new versioning scheme.

This means the version progression for stable releases will now go something like this: ..., 2.0.20, 2.0.22, 2.24.0, 2.24.1, 2.26.0, ...

As a result, the pkg-config check for sdl2 >= 2.0.1 sdl2 < 2.1.0 in ffmpeg should just be sdl2 >= 2.0.1, to allow use of future stable releases.

The intention is that the first release that is not backwards-compatible with SDL 2.0.0 will be labelled as SDL 3, and won't ship sdl2.pc any more.

[Balling]

It also looks like sdl broke fullscren of ffplay.exe... :)

[Simon McVittie]

If there's a regression in newer SDL versions, please report it at ​https://github.com/libsdl-org/SDL with the details.

[Marton Balint]

Fixed in e5163b1d34381a3319214a902ef1df923dd2eeba.

[Simon McVittie]

Thanks, that change looks good.

Having the "sdl2 < 3.0.0" maximum version is harmless, but redundant, because the plan is that when SDL breaks compatibility, the .pc file will be renamed (most likely to sdl3.pc) to make the new library parallel-installable with the old one, at which point it won't match a dependency on sdl2 any more: so it should be sufficient to only have the minimum version, something like

test_pkg_config sdl2 "sdl2 >= 2.0.1" SDL_events.h SDL_PollEvent