Bug#580947: chromium-browser from experimental has included h.264 by default?
On Tue, May 11, 2010 at 17:27:31 +0200, Giuseppe Iuculano wrote:
> There was another solution, and this is now adopted in the latest
> experimental package, Compile with use_system_ffmpeg=1 and
> build_ffmpegsumo=0, but use the in-sources include path for headers, see
>  and .
> In this way, chromium doesn't FTBFS but use the system ffmpeg libs (if
> they are available).
If the bundled ffmpeg and the system one aren't binary-compatible, then
this is a horribly broken solution.