On 2014-02-11 19:00:45, Timothy Gu wrote: > On Feb 11, 2014 10:27 AM, "Antoine Beaupré" <anar...@debian.org> wrote: >> >> On 2014-02-11 13:04:53, Timothy Gu wrote: >> > I have experimented with the new --enable-rpath configure option of >> > FFmpeg, and found that it is even possible to install shared libraries >> > alongside Libav, without interrupting Libav headers, programs, or >> > libraries. See my gist: https://gist.github.com/TimothyGu/8533059 >> > >> Hum... isn't that because you install in /usr/local more than -rpath? > > I used /usr/local because if I mess up I can delete the installation > completely. But it should work with /usr.
Understood. >> Besides, -rpath is actually a lintian warning: >> >> http://lintian.debian.org/tags/binary-or-shlib-defines-rpath.html > > The page states that: > > The only time a binary or shared library in a Debian package should set > RPATH is if it is linked to private shared libraries in the same package. > In that case, place those private shared libraries in /usr/lib/*package*. > > That's exactly what's happening here if we'd like to add the ffmpeg > programs but not use the libraries for other packages. Still, shared > libraries are better than statically linking the ffmpeg programs. Ah, right, I see what you mean. I guess it would be better, but I think it's only a marginal gain over a statically linked binary: it would bring some confusion over the purpose of those libraries... Would other packages be allowed to link against them? >> ... so we shouldn't use that, generally. I would rather try to check to >> see if we could sync the packages to make them ABI-compatible. > > I'd be interested in the results. Yeah, I'm not sure I'll get into that now, but I would welcome other brave souls stepping into this. I was merely scratching an itch to watch that silly video after all. :) >> > I have also tried to build http://mpv.io/ with ffmpeg instead of >> > libav, and I received success in doing tthat as well. Build script is >> > in the gist as well. >> >> Thanks for sharing! That will certainly be useful for others. > > It should work for all applications wishing to support FFmpeg, including > VLC. But the PKG_CONFIG_PATH is really not optimal. That, and -rpath is designed for private libraries, so I don't think that could end up in the archive legitimately. A static link, on the other hand, may have a legitimate purpose. A. -- Advertisers, not governments, are the primary censors of media content in the United States today. - C. Edwin Baker
pgpzopn_xQkS4.pgp
Description: PGP signature
