On Fri, Mar 8, 2013 at 9:48 AM, Brian Matherly <pez4br...@yahoo.com> wrote:
>>>  Dan,
>
>>>
>>>  MLT no longer compiles against libav master:
>>>
>> http://build.mltframework.org/viewLog.html?buildId=5181&tab=buildResultsDiv&buildTypeId=bt8#testNameId7141567987626138055
>>>
>>>  Looks like some stuff got renamed or went away. I think this commit is
>> probably the cause:
>>>
>> http://git.libav.org/?p=libav.git;a=commit;f=libavformat/version.h;h=d8b31be6caebd8d1321ecb754b6e7daaf81dc111
>>>
>>>  You usually take care of this stuff. But let me know if you want me to dig
>> in.
>>
>> I think we need to see what happens to FFmpeg now. IOW, will it adopt
>> those changes largely as-is? Or, is this the "straw that breaks the
>> camel's back" when it comes to practical API compatibility between the
>> forks?
>
> FFMPEG will be following. It's a ticking time bomb right now.
>
> The version update in libav from 54 to 55 switches off a bunch of FF_API_* 
> defines. Look at the defines at the bottom of the file:
> http://git.libav.org/?p=libav.git;a=blob;f=libavformat/version.h;h=52e47820081421f62cd37250beb45cbf72069d61;hb=d8b31be6caebd8d1321ecb754b6e7daaf81dc111
>
> FFMPEG has exactly the same defines conditional on version < 55 and they are 
> poised to go from 54 to 55 any time:
> http://git.videolan.org/?p=ffmpeg.git;a=blob;f=libavformat/version.h;h=672b9003bffaf5c25082ec7654767bde8d6d7a4f;hb=HEAD
>
> We will need to switch to using the non-deprecated constructs that are 
> switched on/off by those defines. When we do, both ffmpeg and libav will work 
> properly.
>

I figured that was the case - that deprecated stuff is finally gone,
at least by default - but I was referring to the new API related to
buffer references. This morning, Michael Niedermayer announced on the
the ffmpeg-devel mailing list that he has made a 1.2 branch in the git
repo to prepare a final release before merging this API change from
libav. So, yes, it does seem they will accept it as-is...  until
perhaps it has had more scrutiny by Michael, which is what my real
concern is. :-)

> In my mind, the real question is whether this is the straw that causes us to 
> drop compatibility with some older ffmpeg versions - in order to clean out 
> some of the #ifdefs in the code.
>

Yeah, I do want to do that because it will be too messy otherwise.

-- 
+-DRD-+

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Mlt-devel mailing list
Mlt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlt-devel

Reply via email to