On Thu, 17 Jan 2013, Reinhard Tartler wrote:
On Wed, Jan 16, 2013 at 7:08 PM, Ronald S. Bultje <[email protected]> wrote:
Hi,
On Jan 16, 2013 10:01 AM, "Justin Ruggles" <[email protected]> wrote:
On 01/16/2013 12:46 PM, Ronald S. Bultje wrote:
Hi,
On Jan 16, 2013 9:43 AM, "Luca Barbato" <[email protected]
<mailto:[email protected]>> wrote:
On 16/01/13 11:46, Luca Barbato wrote:
From: "Ronald S. Bultje" <[email protected]
<mailto:[email protected]>>
Signed-off-by: Luca Barbato <[email protected]
<mailto:[email protected]>>
---
Rebased and compile-tested on arm and powerpc.
Will be pushed in a while if nobody is against it.
I had a question for Justin: the prefix is avpriv_, so is order in
context part of abi? What about size?
I'm not completely sure. The header is not installed so it's not public,
so the only question I think is with mixing non-matching library versions.
avpriv matches av* and thus is part of the exported symbols.
Therefore, adding such a symbol warrants bumping minor (not major).
please do that before pushing.
mixing non-matching library version becomes interesting when you bump
major. However, since all those symbols get proper symbol versions
attached nowadays, this is no problem either.
It's not all that simple - the point here is that they're adding new
fields in a private struct (which is used in the implicit private ABI
between lavu and the others in this case) inbetween existing members. This
means that an old lavc that tries to use members from the floatdsp context
in a newer lavu will end up getting the wrong members.
If the members are added at the end, there shouldn't be too much of an
issue though.
// Martin
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
