On Wed, Dec 10, 2014 at 2:20 PM, Rémi Denis-Courmont <[email protected]> wrote:
> /!\ DO NOT MERGE YET ! /!\ This depends on a pending libvdpau patch.
> ---
> libavcodec/vdpau.h | 3 +++
this calls for a version bump
> libavcodec/vdpau_h264.c | 19 +++++++++++++++++++
> libavcodec/vdpau_internal.h | 3 +++
> 3 files changed, 25 insertions(+)
>
> diff --git a/libavcodec/vdpau.h b/libavcodec/vdpau.h
> index 4244d15..d0194b0 100644
> --- a/libavcodec/vdpau.h
> +++ b/libavcodec/vdpau.h
> @@ -63,6 +63,9 @@ union AVVDPAUPictureInfo {
> VdpPictureInfoMPEG1Or2 mpeg;
> VdpPictureInfoVC1 vc1;
> VdpPictureInfoMPEG4Part2 mpeg4;
> +# ifdef VDP_DECODER_PROFILE_H264_HIGH_444_PREDICTIVE
> + VdpPictureInfoH264Predictive h264_predictive;
> +# endif
> };
> #endif
I am afraid that an ifdef'd member in a public struct (even if
deprecated) is bound to cause troubles for abi stability.
Would there be any way to avoid this?
Thanks
--
Vittorio
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
