Bug 183975 - devel/sdl20: update to 2.0.1 broke apps compiled against 2.0.0
Summary: devel/sdl20: update to 2.0.1 broke apps compiled against 2.0.0
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Marcus von Appen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 22:50 UTC by Jan Kokemüller
Modified: 2013-11-17 12:34 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kokemüller 2013-11-14 22:50:00 UTC
Programs that have been compiled against the SDL2-2.0.0 package won't work with the 2.0.1 package because the library name changed from libSDL2-2.0.so.0 to libSDL2-2.0.so.1. I think upstream's intent is that programs keep working when there are only minor updates to the SDL library.

Other OSs use libSDL2-2.0.so.0 and libSDL2-2.0.so.0.1.0 for SDL2-2.0.1, keeping compatibility with apps linked against 2.0.0.
 - https://www.archlinux.org/packages/extra/x86_64/sdl2/
 - http://koji.fedoraproject.org/koji/rpminfo?rpmID=4545741

Something weird seems to be going on when building on FreeBSD. I will try to investigate further.

How-To-Repeat: - build some application against SDL2-2.0.0
- upgrade SDL to 2.0.1
- application stops working as it can't find libSDL2-2.0.so.0.
Comment 1 Edwin Groothuis freebsd_committer 2013-11-14 22:50:08 UTC
Responsible Changed
From-To: freebsd-ports-bugs->mva

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Marcus von Appen freebsd_committer freebsd_triage 2013-11-14 23:04:23 UTC
Looks like I missed the library change. In contrast to other platforms,
we are relying on cmake as build system. Chances are high that the
library naming is not exactly the same as for the GNU autotools.
I'll check this.

Cheers
Marcus
Comment 3 Marcus von Appen freebsd_committer freebsd_triage 2013-11-17 12:34:31 UTC
State Changed
From-To: open->closed

The issue should be fixed now. Thanks for reporting!