Thu Apr 17 00:28:46 CEST 2008
On Thu, Apr 17, 2008 at 12:05:47AM +0200, Diego Biurrun wrote:
> On Wed, Apr 16, 2008 at 10:52:27PM +0100, M?ns Rullg?rd wrote:
> > Diego Biurrun <diego at biurrun.de> writes:
> > > On Wed, Apr 16, 2008 at 01:12:44PM -0700, Mike Melanson wrote:
> > >>
> > >> I still don't understand libavcodec/dct-test.c. Sure, it looks like a
> > >> standalone utility for testing DCT algorithms. How do I build it? 'make
> > >> libavcodec/dct-test' doesn't to the right thing. Is this tool actually
> > >> supported?
> > >
> > > I fixed this some time ago, it must have become broken during the
> > > non-recursive make rearchitecting. We should have this fixed in short
> > > order. Mans tells me he is working on it. I better hurry up writing
> > > this mail, else he will commit a fix before I finish it...
> > Mostly fixed. cpuid-test still isn't built properly since it isn't
> > picked up by the generic rules. I don't think it ever was, though.
> It definitely used to work. I fixed this some time ago.
So I've copied i386/cputest.c to cpu-test.c and modified the relevant
line in libavcodec/Makefile to
$(SUBDIR)cpu-test$(EXESUF): $(SUBDIR)cpu-test.o $(SUBDIR)$(LIBNAME)
$(SUBDIR)fft-test$(EXESUF): $(SUBDIR)fft-test.o $(SUBDIR)$(LIBNAME)
which is an exact analog of fft-test. fft-test builds fine, cpu-test
does not get built...
More information about the ffmpeg-devel