On Sun, Mar 06, 2016 at 08:43:15AM -0500, Ronald S. Bultje wrote: > Hi, > > On Sat, Mar 5, 2016 at 5:34 PM, Reimar Döffinger <reimar.doeffin...@gmx.de> > wrote: > > > FFmpeg currently lacks a fallback inflate algorithm > > when zlib is not available. > > > > This wouldn't be the first time we NIH'ed something, so that by itself > isn't a sufficiently good reason to not use it :) > > We have a lot of infrastructure for it already available > > though, like VLC code reading (though only in libavcodec, > > not libavutil). > > This is a hackish quick-and-dirty version. > > It certainly is not optimized, and I would want it to > > be mostly small/simple, not necessarily fast anyway > > as it would at most be a fallback. > > Is there interest in me cleaning up the code and > > integrating it as fallback, or are you all happy > > with zlib and I should drop it? > > > Well, you skim over performance, it'd be nice to get some figures of how > much faster/slower it is. Binary size may also be a factor in some > situations (if zlib is included static). >
> How often is zlib not available? I mean, afaik, it's even present on MSVC > builds or iPhone/Android builds. I think we sort of have to quantify how > much of an issue this really is. its probably missing in some self made cross build/testing environments. having our own should mean that some fate clients could test more code also there was at least one case with some memory debugger where i had to rebuild zlib to use it, i dont remember which that was though [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
