On Wed, Oct 7, 2009 at 11:34 AM, Albert J. Wong (王重傑)
<ajw...@chromium.org>wrote:
> We just noticed that the Chromium Helper.app cannot locate the ffmpeg
> binaries (libav*.dylib) in Mac Chromium. This leads to the video feature
> being disabled. :(
> Where should the ffmpeg binaries go? Should they be put alongside the
> binary in the Chromium Helper.app/Contents/MacOS? If we do this, I think it
> will break --single-process mode unless we keep a copy of the binary in both
> spots (which is ugly).
>
If it helps, I believe --single-process is disabled for Google Chrome builds
-- maybe a non issue and simply an inconvenience to us working on Mac
<video>?
>
> Is there a shared location that both application bundles will be able to
> search for the ffmpeg binaries?
>
> -Albert
>
>
> P.S. The reason this wasn't noticed earlier is that all the video devs have
> been executing the app either by setting DYLD_LIBRARY_PATH in their
> environment manually, or via Xcode -- which sets DYLD_LIBRARY_PATH to
> include the output directory, again allowing for resolution of the ffmpeg
> binaries. Using --single-process also avoids this issue since it doesn't
> use Chromium Helper. *sigh*
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
