Bug#729203: ffmpeg alongside libav

On Feb 11, 2014 4:09 PM, "Antoine Beaupré" @ debian.org > wrote: > > On 2014-02-11 19:00:45, Timothy Gu wrote: > > On Feb 11, 2014 10:27 AM, "Antoine Beaupré" @ debian.org > wrote: > >> > >> On 2014-02-11 13:04:53, Timothy Gu wrote: > >> > I have also tried to build http:// > >> >

Bug#729203: ffmpeg alongside libav

On 2014-02-11 19:25:57, Anssi Hannula wrote: > Well, statically linking all the four ff* executables of ffmpeg would > quadruple the total size due to duplication, and the libraries already > take over 10MB even without that... Point taken, patches / pull requests / git send-email welcome. :P Not

Bug#729203: ffmpeg alongside libav

12.02.2014 02:09, Antoine Beaupré kirjoitti: > On 2014-02-11 19:00:45, Timothy Gu wrote: >> On Feb 11, 2014 10:27 AM, "Antoine Beaupré" wrote: >>> >>> Besides, -rpath is actually a lintian warning: >>> >>> http://lintian.debian.org/tags/binary-or-shlib-defines-rpath.html >> >> The page states that

Bug#729203: ffmpeg alongside libav

On 2014-02-11 19:00:45, Timothy Gu wrote: > On Feb 11, 2014 10:27 AM, "Antoine Beaupré" 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 >> > a

Bug#729203: ffmpeg alongside libav

On Feb 11, 2014 10:27 AM, "Antoine Beaupré" 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 header

Bug#729203: ffmpeg alongside libav

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.