On Fri, Jun 12, 2009 at 4:50 PM, Eric Seidel <[email protected]> wrote:
> > Can we do something nice like WebKit does and copy the dlls (from the > installed Chrome or wherever) to next to the build test_shell before > running? Recalling from memory... you should be able to specify a gyp dependency on /third_party/ffmpeg/ffmpeg.gyp:ffmpeg_binaries, which will copy the DLLs alongside the target exe if they're present (they won't be for vanilla chromium checkouts, I have something planned to address this). I'm not a gyp expert, but test_shell might already be including this dependency via the media library Andrew > > > On Fri, Jun 12, 2009 at 4:43 PM, Alpha Lam<[email protected]> wrote: > > (This only applies to Windows, if you are not developing on Windows and > you > > don't care about layout tests, you can stop reading now.) > > Hi all, > > I enabled about 150 layout tests for media today, they are mostly > > sitting inside: > > webkit/data/layout_tests/LayoutTests/media > > webkit/data/layout_tests/LayoutTests/fast/media > > webkit/data/layout_tests/LayoutTests/http/tests/media > > test_shell.exe requires the following DLLs to enable <audio> and > > <video>: > > avcodec-52.dll > > avformat-52.dll > > avutil-50.dll > > If you don't have all of the above DLLs sitting next to > test_shell.exe > > you will expect <audio> and <video> layout tests to all fail. If you > don't > > care about <audio> and <video> you can safely ignore all these failures. > > Alpha > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
