The libmfx deprecation warning tells you to build against libmfx 1.x,
but the actual solution is to use --enable-libvpl instead of using
--enable-libmfx. Update the warning message to reflect this.
Signed-off-by: Leo Izen <leo.i...@gmail.com>
---
configure | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/configure b/configure
index 8a1a1b8584..97b3b29ae5 100755
--- a/configure
+++ b/configure
@@ -6730,8 +6730,7 @@ elif enabled libmfx; then
{ require libmfx "mfxvideo.h mfxdefs.h" MFXInit "-llibmfx
$advapi32_extralibs" &&
{ test_cpp_condition mfxdefs.h "MFX_VERSION >= 1028 && MFX_VERSION <
2000" || die "ERROR: libmfx version must be >= 1.28 and < 2.0"; } &&
warn "using libmfx without pkg-config"; } } &&
- warn "build FFmpeg against libmfx 1.x, obsolete features of libmfx such as
OPAQUE memory,\n"\
- "multi-frame encode, user plugins and LA_EXT rate control mode are
enabled"
+ warn "libmfx is deprecated. Please run configure with --enable-libvpl to
use libvpl instead."
elif enabled libvpl; then
# Consider pkg-config only. The name of libmfx is still passed to
check_pkg_config function for --enable-libvpl option
# because QSV has dependency on libmfx, we can use the same dependency if
using libmfx in this check. The package name
--
2.42.0
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
