2013/3/30 Alex Cohn <[email protected]> > On 30 Mar 2013 20:35, "Lars Hammarstrand" <[email protected]> > wrote: > >> If the crash is reproducible with FFmpeg, you don't need xbmc to test. > > Sounds very good, but how? With the ffmpeg tools (ffplay, etc) as a > stand alone package directly on ios? > Exactly. This makes search for the problematic commit much easier, and > also helps to fix it.
Cool - didn't know that ffplay was able to run on ios "bare-metal" !! Ssh to the device and start ffplay, just that simple? Must test this at once... :) > Question. Most implementations of ffmpeg for ios I've found so far > utilizes static ffmpeg libs (like xbcm do). Is there a known problem to use > ffmpeg as dylibs on ios? > > Static libs are much easier in building, using, and debugging. Shared libs > are cool if the OS supports easy ways to reuse them, and upgrade > independently from the application that uses them, thus reducing the > maintenance efforts (e.g. when a security patch is made for ffmpeg libs). > > Unfortunately, iOS does not provide such mechanisms. That's why shared > ffmpeg libs are rarely used on this platform. > Ok, thanks. I'll guess that the apple devs are performing some non disclosure magic to make their libs to function as dylibs... -- BR Lars.
_______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
