I don't know, but since this is a pretty developement-level question,
you might get a better answer on chromium-dev.
Nico
> --
> Chromium Discussion mailing list: chromium...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-discuss
>
Of course, shortly after sending this I found out what was going on. There is a ifdef guard in net/base/mime_util.cc that evidently caused the relevant mime types to be ignored. Kind of difficult to find. I wonder, why there is this hard coded list instead of simply asking ffmpeg "can you decode this"?
On Wed, Feb 3, 2010 at 2:12 PM, James Willcox <sn...@snorp.net> wrote:
Hi,
I am trying to build Chromium with support for H.264 video support enabled. AFAICT, it looks like adding ffmpeg_branding=Chrome to the gyp defines should be all that is necessary. This does build the relevant ffmpeg bits, but I still have no H.264 support in HTML5 videos. A little help? What else do I need to do?
Thanks,
James