GNOME Bugzilla – Bug 685479
build system not linking binaries properly
Last modified: 2013-02-19 15:09:39 UTC
When building rygel in debian, the packaging tools gives alot of warnings about binaries being uselessly linked to libraries it doesn't use, and thus causing extra package dependencies (and runtime/startup overhead?). A big source of this is the convenience "groups" in common.am which is used in different parts of rygel but doesn't actually match what is often needed. Also there are some places which simply links to libraries not needed.
There is also a problem of rygel not linking to libraries it does use! A separate bug has been filed for that, see Bug #685478
Created attachment 225790 [details] [review] 0001-Drop-unused-libs-from-librygel-core.patch
Created attachment 225791 [details] [review] 0002-Move-rygel-base-libs-up-the-linking-chain-to-avoid-e.patch
Created attachment 225792 [details] [review] 0003-Expand-LIBADDs-to-everything-needed.patch
Created attachment 225793 [details] [review] 0004-Fix-typo-in-librygel-core-Makefile.am-GIO_LIBS-vs-LI.patch
Created attachment 225794 [details] [review] 0005-LIBGUPNP_DLNA_LIBS-is-already-part-of-RYGEL_COMMON_S.patch
Created attachment 225795 [details] [review] 0006-Move-UUID_LIBS-to-where-it-s-actually-used.patch
Created attachment 225796 [details] [review] 0007-Move-GSTREAMER_BASE_LIBS-to-librygel-server-LIBADD.patch
1-7 are the first set of patches (not solving the problem entirely, but getting the easy stuff and worst offenders causing multiple binaries to get uselessly linked) not fixing all of the uselessly linked libraries, but a good start.
Most of them are applied to master now, 0.16 to follow
Comment on attachment 225794 [details] [review] 0005-LIBGUPNP_DLNA_LIBS-is-already-part-of-RYGEL_COMMON_S.patch Think this is not necessary anymore
I think that's either fixed or obsoleted by the build system changes