On Sun, Mar 25, 2018 at 04:35:12PM +0100, Josh de Kock wrote: > On 2018/03/25 16:21, Michael Niedermayer wrote: > >On Fri, Mar 23, 2018 at 11:05:22AM +0100, Nicolas George wrote: > >>Josh de Kock (2018-03-22): [...] > > >People would just start to switch to the current API only to have it > >deprecated in the release after that and having to replace it again > > > >If the new API stays then I will most likely have to submit some ugly > >hack to workaround > >the size explosion issue for static linking with the current API. >
> What size explosion? the one for tools/target_dec_fuzzer It links everything instead of just one codec after the changes, that makes it substantially bigger > > >And that for each lib not just avcodec. > >Thats to allow the ffmpeg ossfuzz code to grow and test more things > >quickly within the available resources. > I honestly would like to be an idealist here, but it's much more practical > to just be real here. Nothing happens in this project unless the > conversation begins with a patch (and even then, stuff barely happens). So > in the words of others on the list: > > You forgot to attach your patch. yes, ill likely write&post that in case the API is not reverted. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
