On 4/30/12 7:42 PM, Mike Gilbert wrote: > ffmpeg upstream is not afraid of making API changes, so it has proven > quite difficult to make chromium work with all versions on ffmpeg in > portage, plus the bundled snapshot. When we were using the system lib, > it would break nearly every time a new major version of chromium was > forked.
Right. Eventually I'd like to create an ffmpeg compatibility layer in Chromium, so that all Chromium-specific code would talk to it, and the layer would know how to handle (at compile time) different versions of ffmpeg. Also, the browser binary should really just link directly to ffmpeg libraries instead of using dlopen. I also plan to change that.
signature.asc
Description: OpenPGP digital signature
