aboutsummaryrefslogtreecommitdiffstats
path: root/libavutil/cpu.h
diff options
context:
space:
mode:
authorHaihao Xiang <haihao.xiang@intel.com>2021-02-03 09:08:27 +0800
committerHaihao Xiang <haihao.xiang@intel.com>2022-08-12 10:43:39 +0800
commitfea5aed2796e27377243c9d6fb5a85b5f4952746 (patch)
tree12ddb9eadfb059bbe3805597e5fbeab8ba84a281 /libavutil/cpu.h
parent3443330b172af9b45e11ecc3af4351a023f83d9c (diff)
downloadffmpeg-fea5aed2796e27377243c9d6fb5a85b5f4952746.tar.gz
configure: ensure --enable-libmfx uses libmfx 1.x
Intel's oneVPL is a successor to MediaSDK, but removed some obsolete features of MediaSDK[1], some early versions of oneVPL still use libmfx as library name[2]. However some of obsolete features, including OPAQUE memory, multi-frame encode, user plugins and LA_EXT rate control mode etc, have been enabled in QSV, so user can not use --enable-libmfx to enable QSV if using an early version of oneVPL SDK. In order to ensure user builds FFmpeg against a right version of libmfx, this patch added a check for version < 2.0 and warning message about the used obsolete features. [1] https://spec.oneapi.io/versions/latest/elements/oneVPL/source/VPL_intel_media_sdk.html [2] https://github.com/oneapi-src/oneVPL
Diffstat (limited to 'libavutil/cpu.h')
0 files changed, 0 insertions, 0 deletions