From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: remove usage of internal deprecation macro
Date: Wed, 16 Mar 2022 07:57:14 -0300
Message-ID: <ccef74dd-e7d7-0ee0-72ec-518c479cb81d@gmail.com> (raw)
In-Reply-To: <AS1PR01MB956479437291C0A5B319D1548F119@AS1PR01MB9564.eurprd01.prod.exchangelabs.com>
On 3/16/2022 7:15 AM, Andreas Rheinhardt wrote:
> James Almer:
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>> fftools/ffmpeg.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
>> index a98e49b775..3b625a9918 100644
>> --- a/fftools/ffmpeg.c
>> +++ b/fftools/ffmpeg.c
>> @@ -2880,9 +2880,9 @@ static int init_input_stream(int ist_index, char *error, int error_len)
>> ist->dec_ctx->opaque = ist;
>> ist->dec_ctx->get_format = get_format;
>> #if LIBAVCODEC_VERSION_MAJOR < 60
>> -FF_DISABLE_DEPRECATION_WARNINGS
>> + AV_NOWARN_DEPRECATED({
>> ist->dec_ctx->thread_safe_callbacks = 1;
>> -FF_ENABLE_DEPRECATION_WARNINGS
>> + })
>> #endif
>>
>> if (ist->dec_ctx->codec_id == AV_CODEC_ID_DVB_SUBTITLE &&
>
> AV_NOWARN_DEPRECATED currently doesn't work with Clang; so you first
> need to find out from which version onward it supports these macros.
Does not work in what way? Not compile, or just be a no-op?
If the latter, then that's a limitation FF_DISABLE_DEPRECATION_WARNINGS
also has for some targets. We're not going to stop using a macro just
because it does nothing in some scenarios.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-03-16 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 21:15 James Almer
2022-03-16 10:15 ` Andreas Rheinhardt
2022-03-16 10:57 ` James Almer [this message]
2022-03-16 12:58 ` Andreas Rheinhardt
2022-03-16 13:07 ` James Almer
2022-03-16 13:10 ` Andreas Rheinhardt
2022-03-16 13:14 ` James Almer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccef74dd-e7d7-0ee0-72ec-518c479cb81d@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git