[FFmpeg-devel] [PATCH 1/2] avcodec/h264_parse: change prefix to avpriv for usage in avformat mxf muxer
Baptiste Coudurier
baptiste.coudurier at gmail.com
Wed Apr 3 15:25:57 EEST 2019
Hey Hendrik
> On Apr 3, 2019, at 11:37 AM, Hendrik Leppkes <h.leppkes at gmail.com> wrote:
>
> On Wed, Apr 3, 2019 at 11:22 AM Baptiste Coudurier
> <baptiste.coudurier at gmail.com> wrote:
>>
>> ---
>> libavcodec/cbs_h2645.c | 28 ++++++++++++++--------------
>> libavcodec/extract_extradata_bsf.c | 4 ++--
>> libavcodec/h2645_parse.c | 6 +++---
>> libavcodec/h2645_parse.h | 6 +++---
>> libavcodec/h264_parse.c | 4 ++--
>> libavcodec/h264_parser.c | 4 ++--
>> libavcodec/h264_ps.c | 4 ++--
>> libavcodec/h264_ps.h | 4 ++--
>> libavcodec/h264_slice.c | 2 +-
>> libavcodec/h264data.c | 2 +-
>> libavcodec/h264data.h | 3 ++-
>> libavcodec/h264dec.c | 10 +++++-----
>> libavcodec/hevc_parse.c | 2 +-
>> libavcodec/hevc_parser.c | 4 ++--
>> libavcodec/hevcdec.c | 4 ++--
>> libavcodec/svq3.c | 2 +-
>> 16 files changed, 45 insertions(+), 44 deletions(-)
>>
>
> We prefer not to expose huge modules like this as avpriv, as it makes
> it part of the ABI and as such impossible to change without
> deprecation cycles.
> Preferably, avpriv should be avoided entirely where possible, as it
> has many of the same limitations as actual public API, and just adds
> confusion.
Understood. What’s the alternative ?
Thanks!
—
Baptiste
More information about the ffmpeg-devel
mailing list