Bump to libavif 1.1.1#742
Conversation
|
Also bump aom to latest revision of v3.6.1-SDL |
|
P.S: Can you do the same for SDL2_image? |
|
P.S.: Does libavif properly find and use our vendored sharpyuv ? |
150468a to
d17cfa5
Compare
It didn't at first, but now it does. |
|
I think this P/R (and its SDL2 counterpart) are ready for merge. I generated x86 and x64 libavif dlls, run-tested under win11-x64. One thing I noticed is the possible winpthreads dll dependency |
|
If you're talking about libsdl-org/libavif@3567afd, it's only added for non-Windows platforms. |
Yup :)
I guess so. I built my dlls w/o removing it, but my toolchains don't have winpthreads. |
Maybe we can guard |
I see this in #if defined(_WIN32)
tdata->thread = (HANDLE)_beginthreadex(/*security=*/NULL,
/*stack_size=*/0,
&avifImageYUVToRGBThreadWorker,
tdata,
/*initflag=*/0,
/*thrdaddr=*/NULL);
return tdata->thread != NULL;
#else
// TODO: Set the thread name for ease of debugging.
return pthread_create(&tdata->thread, NULL, &avifImageYUVToRGBThreadWorker, tdata) == 0;
#endifOn MSVC and MINGW, it uses |
Sounds like it |
|
Commenting out --- CMakeLists.txt~
+++ CMakeLists.txt
@@ -613,4 +613,4 @@
-if(UNIX OR MINGW)
+if(UNIX) # OR MINGW
# Find out if we have threading available
set(THREADS_PREFER_PTHREAD_FLAG ON)
find_package(Threads) |
Does it have an alternate Win32 threading implementation? Otherwise this will be a performance regression (assuming previous builds had threading) |
Yes (see reformat.c)
Previous version was the same. It is some unfothpmable that that MINGW+pthread check |
|
I updated libavif cmake'ry and also updated the Xcode project file along the way. (Did the same in SDL2 version.) Will merge when the CI is all green. |
|
Thanks sezero for taking care of this |
Got it, thanks for clarifying. |
Fixes #740