On Wed, May 25, 2011 at 14:46:56 (CEST), Diego Biurrun wrote: > On Wed, May 25, 2011 at 08:23:31AM -0400, Ronald S. Bultje wrote: >> >> On Wed, May 25, 2011 at 8:14 AM, Diego Biurrun <[email protected]> wrote: >> > On Fri, May 20, 2011 at 08:49:20PM +0200, Diego Biurrun wrote: >> >> On Thu, May 12, 2011 at 05:30:04PM +0200, Diego Biurrun wrote: >> >> > >> >> > First off, it would be great to have a Cygwin FATE configuration again. >> >> > People do use Cygwin and we would profit from timely notification of >> >> > breakage. >> >> >> >> Ronald would like to see FATE instances for >> >> >> >> - "THREAD_TYPE=2 THREADS=8 fate" >> >> - "THREAD_TYPE=1 THREADS=8 fate" >> >> >> >> I would like to have another one that enables all external libraries. >> >> Not all developers have all supported external libraries installed, >> >> so it's easy for breakage to slip through, as apparently just >> >> happened for libmp3lame. >> > >> > Anyone? >> >> Mans added one threading fate box. > > Does that cover all your requirements? > > I'd still like to see that external libraries FATE box.
We also have the ubuntu autobuilds: https://launchpad.net/~motumedia/+archive/libav-daily/+packages These builds are supposed to be very similar to what I use in the distro packages, i.e., many external libraries are enabled. Hm, it seems that libmp3lame is missing for some reason, looking into that now. I could also run fate during those builds as well, but unfortunately, these builds are isolated and do not have access to the internet. This means I have to upload a fate package with the samples and the results cannot be pushed back, at least not automatically. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
