On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote:
> On Fri, Oct 19, 2012 at 07:26:02PM +0200, Diego Biurrun wrote:
> > [...]
>
> I'm mostly done with FATE dependencies and have some 50 patches in
> need of cleaning locally.
>
> There are a bunch of parts required by most or a large number of FATE
> tests. I'm not quite sure how to handle them, here's a list
>
> rawvideo:
>
> decoder, demuxer, encoder
>
> filters:
>
> afifo, anull, fifo, null, resample
not format? we have quite a few video sample tests which require it,
tests of rgb codecs for example. Ah, I see, avconv depends already on it
inconfigure. afifo, anull, fifo, null might be candidates to always
enable in libavfilter.
> muxers:
>
> crc, framecrc, framemd5, md5, rawvideo
>
> protocols:
>
> file, md5, pipe
>
> Plus PCM_S16LE muxer and decoder, which is required by a large number of
> audio tests.
>
> There are multiple ways to handle these more general components:
>
> - have avconv directly depend on some or all of them
In configure or just for FATE_AVCONV? The second sounds reasonable
> - just add all these components to individual deps
that sounds insane
> - have a group of "FATE deps" that get enabled automatically
what does that mean? making it impossible to disable the file protocol
for example?
> - have a group of "FATE deps" that get enabled via a configure switch
That is a good idea regardlessly. using something like
.../configure --disable-everything --enable-decoder=h264 \
--enable-demuxer=h264 --enable-fate-minimal
and being able to run make fate-h264 would be nice. Having a good test
coverage for a --disable-random is probably also a good idea.
> - ...
Then there are obvious groups of tests which share dependency then just
adding the dependency for that group.
Janne
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
