[FFmpeg-devel] [PATCH] restoring binary compatibility with ffmpeg 0.5

Reinhard Tartler siretart
Wed Jun 9 10:42:33 CEST 2010

On Wed, Jun 09, 2010 at 10:18:30 (CEST), M?ns Rullg?rd wrote:

> Reinhard Tartler <siretart at tauware.de> writes:
>> we are talking about public symbols only here. Since libavformat always
>> includes libavcodec's public headers, you will always get redeclarations
>> errors for the offending function.  Putting them in a seperate
>> compilation unit that does not include libavcodec's public headers won't
>> work either, because the implementation of these compat symbols would
>> just call the now moved symbols.
>> IMO the proper solution for this scenario is to
>> add  foobar@@libavcodec1 in libavcodec
>> add  ff_compat_foobar@@libavformat1 in libavformat that just calls foobar at libavcodec1
>> add  foobar at libavformat1 as alias in libavformat
>> NB: the syntax '@@' vs. '@'.
>> I still claim that step 3 is supported by all relevant platforms, even
>> ARM RVCT. Any counterexamples?
> Step 3?

I have shown you a link to the documentation that shows by example how
to implement step 3 with the ARM RVCT toolchain. What else do you want

Reinhard Tartler, KeyID 945348A4

More information about the ffmpeg-devel mailing list