On 19.07.2022 13:34, Timo Rothenpieler wrote:
On 19.07.2022 09:25, Mark Himsley wrote:
On Sun, 17 Jul 2022 at 12:37, Timo Rothenpieler
<t...@rothenpieler.org> wrote:
I will push this series tonight, in about 8 hours from now.
Last chance to delay this by reviewing or raising related concerns.
Just FYI - this broke my nightly automated builds - which
cross-compile on Linux for Windows.
x86_64-w64-mingw32-gcc -I. -I./ --static -static -static-libstdc++
-static-libgcc -DPTW32_STATIC_LIB -D_WIN32_WINNT=0x0600
-I/opt/ffbuild/include -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64
-D_LARGEFILE_SOURCE -U__STRICT_ANSI__ -D__USE_MINGW_ANSI_STDIO=1
-D__printf__=__gnu_printf__ -D_POSIX_C_SOURCE=200112
-D_XOPEN_SOURCE=600 -DPIC -DOPJ_STATIC -DZLIB_CONST -DHAVE_AV_CONFIG_H
-DBUILDING_avfilter --static -static -static-libstdc++ -static-libgcc
-DPTW32_STATIC_LIB -D_WIN32_WINNT=0x0600 -I/opt/ffbuild/include
--static -static -static-libstdc++ -static-libgcc -DPTW32_STATIC_LIB
-D_WIN32_WINNT=0x0600 -std=c11 -fomit-frame-pointer -pthread
-I/opt/ffbuild/include -I/opt/ffbuild/include -I/opt/ffbuild/include
-I/opt/ffbuild/include/freetype2 -I/opt/ffbuild/include
-I/opt/ffbuild/include/libpng14 -I/opt/ffbuild/include/openjpeg-2.4
-I/opt/ffbuild/include/opus -I/opt/ffbuild/include/opus
-I/opt/ffbuild/include -I/opt/ffbuild/include
-I/opt/ffbuild/include/srt -I/opt/ffbuild/include
-I/opt/ffbuild/include -I/opt/ffbuild/include -I/opt/ffbuild/include
-I/opt/ffbuild/include -I/opt/ffbuild/include -I/opt/ffbuild/include
-I/opt/ffbuild/include -I/opt/ffbuild/include -I/opt/ffbuild/include
-DLIBXML_STATIC -I/opt/ffbuild/include/libxml2 -I/opt/ffbuild/include
-g -Wdeclaration-after-statement -Wall -Wdisabled-optimization
-Wpointer-arith -Wredundant-decls -Wwrite-strings -Wtype-limits
-Wundef -Wmissing-prototypes -Wstrict-prototypes -Wempty-body
-Wno-parentheses -Wno-switch -Wno-format-zero-length -Wno-pointer-sign
-Wno-unused-const-variable -Wno-bool-operation -Wno-char-subscripts
-O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize
-Werror=format-security -Werror=implicit-function-declaration
-Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat
-fdiagnostics-color=auto -Wno-maybe-uninitialized -MMD -MF
libavfilter/vsrc_ddagrab.d -MT libavfilter/vsrc_ddagrab.o -c -o
libavfilter/vsrc_ddagrab.o libavfilter/vsrc_ddagrab.c
libavfilter/vsrc_ddagrab.c: In function 'init_dxgi_dda':
libavfilter/vsrc_ddagrab.c:157:36: error: expected declaration
specifiers or '...' before '*' token
157 | typedef DPI_AWARENESS_CONTEXT
(*set_thread_dpi_t)(DPI_AWARENESS_CONTEXT);
| ^
I'm honestly not sure what this is complaining about.
Does it not know the DPI_AWARENESS_CONTEXT enum?
I added an explicit configure check for that type.
Definitely odd, IDXGIOutput5 and it are both Windows 10 APIs, so I'd
have expected them to always exist in tandem.
You might want to update or repair your weird Windows SDK.
_______________________________________________
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".
