Re: chromium-browser from experimental has included h.264 by default?

[Ben Hutchings <ben@decadent.org.uk>]

On Tue, May 11, 2010 at 05:27:31PM +0200, Giuseppe Iuculano wrote:
[...]
> chromium doesn't compile with the current version of ffmpeg in unstable
> because it is too outdated, this means I had three choices:
> 
> - compile with use_system_ffmpeg=0 and build_ffmpegsumo=0 (this means
> drop ffmpeg support)
> - compile with use_system_ffmpeg=1 and build_ffmpegsumo=0 --> FTBFS
> - compile with use_system_ffmpeg=1 and build_ffmpegsumo=1 (this means
> compile and ship ffmpeg-mt)
> 
> 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
> [1] and [2].
[...]

How can you expect this to work?  The ABI of the system ffmpeg libraries
is not going to match the ABI defined by the bundled headers.  You must
patch chromium to work with the system ffmpeg headers.  As an example, see
what I do in dvswitch to work with different ffmpeg versions:

http://git.debian.org/?p=dvswitch/dvswitch.git;a=blob;f=src/avcodec_wrap.h;hb=master

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus