From: Thilo Borgmann <thilo.borgmann@mail.de>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/2] lavfi/coreimage: suppress OpenGL deprecation warning
Date: Sat, 25 Feb 2023 18:48:33 +0100
Message-ID: <b9da4dc1-2a6a-4de4-eb28-d1dcecff2f5e@mail.de> (raw)
In-Reply-To: <20230225152658.3086653-1-mypopydev@gmail.com>
Am 25.02.23 um 16:26 schrieb Jun Zhao:
> From: Jun Zhao <barryjzhao@tencent.com>
>
> suppress OpenGL deprecation warning.
>
> Signed-off-by: Jun Zhao <barryjzhao@tencent.com>
> ---
> libavfilter/vf_coreimage.m | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavfilter/vf_coreimage.m b/libavfilter/vf_coreimage.m
> index b1959861de..17b2cde6fe 100644
> --- a/libavfilter/vf_coreimage.m
> +++ b/libavfilter/vf_coreimage.m
> @@ -22,7 +22,8 @@
> * @file
> * Video processing based on Apple's CoreImage API
> */
> -
> +#define GL_SILENCE_DEPRECATION
> +#define CI_SILENCE_GL_DEPRECATION
> #import <CoreImage/CoreImage.h>
> #import <AppKit/AppKit.h>
Why do you want to silence a framework warning?
-Thilo
_______________________________________________
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:[~2023-02-25 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 15:26 Jun Zhao
2023-02-25 15:26 ` [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: initialize the 'o' to silence the warning Jun Zhao
2023-02-25 17:49 ` Thilo Borgmann
2023-10-09 21:01 ` [FFmpeg-devel] [6.0] Segmentation fault in graph_parse() (was: [PATCH 2/2] fftools/ffmpeg_filter: initialize the) " Dominik 'Rathann' Mierzejewski
2023-02-25 17:48 ` Thilo Borgmann [this message]
2023-02-26 1:42 ` [FFmpeg-devel] [PATCH 1/2] lavfi/coreimage: suppress OpenGL deprecation warning mypopy
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=b9da4dc1-2a6a-4de4-eb28-d1dcecff2f5e@mail.de \
--to=thilo.borgmann@mail.de \
--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