Hi,
If you want to support ffmpeg 0.5 a bit more, you have to known it
fails to build width :
factory.c:49: warning: 'enum AVLockOp' declared inside parameter list
factory.c:49: warning: its scope is only this definition or
declaration, which is probably not what you want
factory.c:49: error: parameter 2 ('op') has incomplete type
factory.c: In function 'avformat_lockmgr':
factory.c:55: error: 'AV_LOCK_CREATE' undeclared (first use in this function)
factory.c:55: error: (Each undeclared identifier is reported only once
factory.c:55: error: for each function it appears in.)
factory.c:59: error: 'AV_LOCK_OBTAIN' undeclared (first use in this function)
factory.c:62: error: 'AV_LOCK_RELEASE' undeclared (first use in this function)
factory.c:65: error: 'AV_LOCK_DESTROY' undeclared (first use in this function)
factory.c: In function 'avformat_init':
factory.c:80: warning: implicit declaration of function 'av_lockmgr_register'
make[3]: *** [factory.o] Error 1
make[3]: Leaving directory
`/build/buildd/mlt-0.7.7+git20120208.de3106c7/src/modules/avformat'
Sunab.
Le 12 février 2012 08:20, Dan Dennedy <d...@dennedy.org> a écrit :
> On Sat, Feb 11, 2012 at 7:48 PM, Brian Matherly <pez4br...@yahoo.com> wrote:
>> Dan,
>>
>> I see that our friends at ffmpeg have changed the libavcodec interface:
>> http://git.videolan.org/?p=ffmpeg.git;a=commit;f=libavcodec/avcodec.h;h=52f82a11489af88960c8774c142cbde78063365f
>>
>> MLT git HEAD currently has two problems when compiled against ffmpeg git
>> HEAD (that I know of)
>> 1) MLT gets deprecation warnings for avcodec_encode_audio() and
>> avcodec_encode_video()
>
> it should be ok for now unless it is needed to fix x264
>
>> 2) MLT does not detect libx264 because it uses the new "encode2" field in
>> AVCodec
>
> but this is a problem
>
>> What's your policy on chasing ffmpeg API changes? Do it right away, or wait
>> for things to calm down?
>
> If it breaks something popular or really needed by some client, do it
> right away.
>
>> There are a lot of "#if LIBAVCODEC_VERSION_INT..." conditionals in the
>> libavformat module. How far back should MLT support with respect to old
>> libav API versions?
>
> I think I want to still support ffmpeg 0.5 a while longer.
>
>> Is this worth holding back whatever release you are working on?
>
> I could say yes, but at this rate, the day after release it can be
> broken again. Still, I do not like the idea of the new release being
> broken when using the build scripts.
>
>> Let me know if you want any help getting the avformat module updated. I'll
>> probably start hacking on it anyway since I would like to see libx264
>> working again.
>
> go for it
>
> --
> +-DRD-+
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Mlt-devel mailing list
> Mlt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mlt-devel
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel
