From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: don't warn deprecated symbols from libvpl
Date: Mon, 4 Dec 2023 04:21:53 +0000
Message-ID: <c1b6c894e1bc4e51c831dd343ed87a5e4f68dad0.camel@intel.com> (raw)
In-Reply-To: <20231127081152.2437803-1-haihao.xiang@intel.com>
On Ma, 2023-11-27 at 16:11 +0800, Xiang, Haihao wrote:
> From: Haihao Xiang <haihao.xiang@intel.com>
>
> libvpl deprecated some symbols (e.g. MFX_EXTBUFF_VPP_DENOISE2 is used to
> replace MFX_EXTBUFF_VPP_DENOISE), however the new symbols aren't support
> by MediaSDK runtime. In order to support the combination of libvpl and
> MediaSDK runtime on legacy devices, we continue to use the deprecated
> symbols in FFmpeg. This patch added -DMFX_DEPRECATED_OFF to CFLAGS to
> silence the corresponding compilation warnings.
>
> Signed-off-by: Haihao Xiang <haihao.xiang@intel.com>
> ---
> configure | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configure b/configure
> index 838e627084..d77c053226 100755
> --- a/configure
> +++ b/configure
> @@ -6776,6 +6776,7 @@ elif enabled libvpl; then
> # is extracted from "vpl >= 2.6"
> check_pkg_config libmfx "vpl >= 2.6" "mfxvideo.h mfxdispatcher.h" MFXLoad
> || \
> die "ERROR: libvpl >= 2.6 not found"
> + add_cflags -DMFX_DEPRECATED_OFF
> fi
>
> if enabled libmfx; then
Will apply,
Thanks
Haihao
_______________________________________________
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".
prev parent reply other threads:[~2023-12-04 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 8:11 Xiang, Haihao
2023-12-04 4:21 ` Xiang, Haihao [this message]
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=c1b6c894e1bc4e51c831dd343ed87a5e4f68dad0.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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