SFML 3 migration - #59623
Conversation
b4d25f5 to
f2d0424
Compare
ahesford
left a comment
There was a problem hiding this comment.
- Commit messages for SFML and CSFML should be reworded to follow the usual form
- Changes to
common/shlibsshould be split by package and part of the respective first two commits - Is this the original source of the
etrpatch? If so, this file should be used as is to preserve attribution. - I'd probably advocate just dropping
etrif it is slow to adapt to new SFML, but defer to @Hoshpak as its maintainer
No it's not. I found this patch https://sourceforge.net/p/extremetuxracer/discussion/general/thread/77659bcd0c/ here, but it was not working so I implemented a Ralph loop to port from scratch. Most of the other patches are also generated by me, with a custom Ralph loop. |
|
It looks like your Ralph loop has stolen at least the patch description whole cloth from the source I linked. |
|
Possibly, I'll add a reference. That patch does not compile at all, though. |
|
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
SFML 3.1.0 migration
Migrate SFML and reverse dependencies to SFML 3.x.
SONAME bump
SFML 3.x introduces a major SONAME break (
libsfml-*.so.2.6->libsfml-*.so.3.1). All reverse dependencies are rebuilt/updated accordingly.common/shlibsupdated for both SFML and CSFML.Version updates
Revbumps (rebuild for SFML 3.1.0)
Notable changes
0001-Port-to-SFML-3.0.patchto port to new SFML APIfix-sfml31-pkgconfig.patchfor SFML 3.1 pkgconfig compatibilityboost-1.80.patch,boost-1.88.patch, andno-scriptdocs-cross.patch(no longer needed with 2.2.0)