[Ffmpeg-devel] RE: Compiling FFmpeg using ISO/C89 compiler
Wed Dec 6 21:13:41 CET 2006
Should I configure using the the long configuration DivX.txt file.
I wonder about the following options:
--disable-encoders --disable-muxers --enable-muxer=ac3 --enable-muxer=avi --enable-muxer=mp3 --enable-dsaac --enable-dsac3 --enable-dsdts --enable-dsrealvideo --enable-wmvdmo --enable-static --disable-shared --enable-memalign-hack
--disable-mpegaudio-hp --enable-encoder=divx --enable-mp3lame --enable-encoder=mp3lame --enable-mp3surround --enable-encoder=mp3surround --enable-avisynth
In my case i am interested the minimum correct functionality for an "mpeg" decoding. It sounds to me that I should make the opposite decisions.
Another "make" trial comes with the following message:
In file included from ~/drffmpeg/export/drffmpeg/common.h:278,
~/drffmpeg/libavutil/internal.h:219: warning: static declaration of 'lrintf' follows non-static declaration
In file included from resample2.c:125:
~/drffmpeg/export/drffmpeg/common.h: In function `av_build_filter':
~/drffmpeg/libavutil/internal.h:219: sorry, unimplemented: inlining failed in call to 'lrintf': redefined extern inline functions are not considered for inlining
~/drffmpeg/export/drffmpeg/common.h:377: sorry, unimplemented: called from here
make: *** [resample2.o] Error 1
make: Leaving directory `~/drffmpeg/libavcodec'
make: *** [lib] Error 2
What do you suggest?
Another question, If I would like to have only the "mpeg1/2/4" audio/video related files to function. what will be the best way to approach the problem.
Date: Wed, 06 Dec 2006 18:35:53 +0100
From: Steve Lhomme <slhomme at divxcorp.com>
Subject: Re: [Ffmpeg-devel] Re: Compiling FFmpeg using ISO/C89
To: FFmpeg development discussions and patches
<ffmpeg-devel at mplayerhq.hu>
Message-ID: <4576FF79.5030906 at divxcorp.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
M??ns Rullg??rd wrote:
> Steve Lhomme said:
>> M??ns Rullg??rd wrote:
>>> Steve Lhomme said:
>>>> Also note that this problem is due to the recent changes (improvements
>>>> ???) to the configure script that consider that everything is available
>>>> for every platform by default.
>>> It does nothing of the kind. The configure script *checks* what is available,
>>> and uses only the things that are found. Moreover, use of most external libs
>>> must be explicitly requested, and only then will they be checked for. Do not
>>> speak in matters of which you do not know.
>> I just checked the official SVN and this behaviour has changed (again)
>> since there is much more code to handle the enabling/disabling of
>> decoders (and others). You probably never looked at the configure script
>> we are talking about (based on some older FFMPEG SVN). So check yourself
>> before pointing fingers around.
> I have not looked at your butchered version, and I have no intention to do so.
> Someone else has already provided ample evidence that it doesn't work properly.
It does work for us on both Windows and Mac which is what we support for
the moment. Our goal is to have the best possible program for our needs,
whatever they may be. If our code happen to be useful for others, that's
good for them, but we will not make compromises with the sole purpose of
doing what FFMPEG should we able to do in the first place.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 7173 bytes
Desc: not available
More information about the ffmpeg-devel