Undefined symbols for architecture x86_64 macOS about libavif HOT 4 CLOSED

Hi, this is now fixed at HEAD: you can fully disable libsharpyuv by setting -DAVIF_LIBSHARPYUV=OFF

from libavif.

Hi, this seems to be a problem with conan as there is no libsharpyuv during linkage. I guess a bug upstream needs to be reported? Maybe here? https://github.com/conan-io/conan-center-index/tree/master/recipes/libavif

from libavif.

@vrabaud, thank you very much, and I apologize for reporting in the wrong repository. For a moment, I thought it was an issue on macOS x86_64.

from libavif.

conan recipe doesn't expose any libsharpyuv lib during build, so I guess it's found on system and incidentally enabled in libavif during build, while this conan recipe assumes that it's not the case.
So I think that the root cause is that libavif CMakeLists doesn't provide a way to really disable optional support of these dependencies (it follows a pattern in which features are enabled if some dependency is found and disabled if not, it's really problematic for package managers), so it can't guarantee reproducible build without heavy patching.
But meanwhile, recipe needs to be fixed, actually patch CMakeLists of libavif, no other choice, or always expose libwebp>=1.3.0 in order to be sure to always get libsharpyuv (it's not unbundled in conancenter) and not something unpredictable from system.

from libavif.