[Bug 727534] cerbero: Add support for non-standard Darwin .dylib filenames

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=727534
  GStreamer | packages | unspecified

Philip Withnall <bugzilla> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla at tecnocode.co.uk

--- Comment #5 from Philip Withnall <bugzilla at tecnocode.co.uk> 2014-04-04 07:47:28 UTC ---
(In reply to comment #3)
> I am not sure this patch is completely correct as .dylib libraries are the
> libraries used at link time, similar to libfoo.so files in linux.
> The problem with this patch is that libfoo.dylib libraries that are now treated
> as link libraries and packaged in the development packages will be also
> packaged in the runtime package.

Looking at the output packages I have here, the dylib has been put in the
runtime package and not the development package. That makes sense to me. It’s
needed at runtime for dynamic loading, and also needed at development time —
but it seems to be entirely reasonable to require the developer to have both
the development and runtime packages available to compile against.

The patch does exactly the same for .dylibs as is already implemented for
Windows DLLs.

> Can you please describe the project creating this kind of library?
> I think the correct fix is in the recipe's post-install step, moving
> libfoo.dylib to libfoo.0.dylib and link libfoo.dylib to libfoo.0.dylib.

The project doesn’t have an SO version (or its Darwin equivalent) set.
Unfortunately, that naming on the library is a requirement of the project, so
can’t be changed. Otherwise we would have done that already. :-(

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.