Building libavif Linker; unresolved external symbols from the libjpeg package

[Arebusf21]

Describe the bug
When building an executable to test the libavif package, I get Linker unresolved external symbol errors, specifically from the included external libjpeg-turbo libraries.

Environment

• OS: Windows 10 Pro
• Visual Studio 2022 Enterprise 64bit - Current.
• V 17.11.5
• Compiler: Visual C++ 2022
• CMake project.

To Reproduce
Steps to reproduce the behavior:

1. build a vs2022 Cmake project and target the libavif package.
2. See the build log.

Expected behavior
Should build without linker unresolved symbols.

Failure logs
-(please attached failure logs)
Session log.txt

Additional context
Built as a Visual Studio 2022 CMake project to test building the libavif package. The project itself can be made available if needed
the libjpeg libraries with the missing modules are in the out\build\x64-Debug\vcpkg_installed\x64-windows\bin folder but the linker can't find them.
CMakeLists.txt file included:
CMakeLists.txt

[Mengna-Li]

@Arebusf21 The latest libavif version is 1.1.1, Please pull the master and try the new release. Thanks.

[Arebusf21]

Thanks for the response.
Ok, so I managed to get the Linker to complete without errors, I have attached the session log.
I had to explicitly specify the library; jpeg.lib in the CMakeLists.txt file for my app, under "target_link_libraries".
I was under the impression that all the dependent libraries would be linked by default, but it makes sense the only the libraries are built
and linking is driven by the app.
Session log.txt

[Mengna-Li]

libavif does not need to link jpeg.lib, upstream has already disabled JPEG finding in libuv.
AOMediaCodec/libavif#2459

[dg0yt]

I think it is not solved. #41666 (comment) was uninformed.

Note: the issue is for using libavif, not for building libavif.