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).
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: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
