From 2a1fd3c84ef9b5d1daf32fd3cbfebff3c5996ef4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20Storsj=C3=B6?= Date: Sat, 23 May 2020 21:14:40 +0300 Subject: [PATCH] mfenc: Fix building with clang in MSVC mode MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Just including icodecapi.h + codecapi.h apparently misses some bits, that MSVC doesn't complain about, but Clang does. Thus add a missing header to the custom hacky include path (required for keeping ICodecAPI visible when building in UWP mode, as it is intended to). The issue in Windows SDK headers about ICodecAPI availability in UWP/app mode has been reported upstream at https://developercommunity.visualstudio.com/content/problem/1037125/icodecapi-not-visible-when-compiling-in-uwp-mode.html, and later also filed in Feedback Hub (which can't be linked to externally). Signed-off-by: Martin Storsjö --- libavcodec/mf_utils.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/libavcodec/mf_utils.h b/libavcodec/mf_utils.h index 39d5844ff6..4373e62ed2 100644 --- a/libavcodec/mf_utils.h +++ b/libavcodec/mf_utils.h @@ -28,6 +28,9 @@ // of including it though, through strmif.h via dshow.h. And on mingw, the // mf*.h headers below indirectly include strmif.h.) #include +// Clang in MSVC mode fails on codecapi.h if we haven't included uuids.h +// before, while it seems to work fine with MSVC itself. +#include #else #include #endif