You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Poco 1.14.0 introduced a dependency on Utf8Proc. However, PocoFoundationConfig.cmake doesn't have a find_dependency call for it.
To Reproduce
Install Poco 1.14.0 with -DPOCO_UNBUNDLED on Linux. Attempt to configure Mumble 1.5.634 against it (Mumble's CMake build system doesn't look for Utf8Proc itself). CMake fails, with the error:
The link interface of target "Poco::Foundation" contains:
Utf8Proc::Utf8Proc
but the target was not found. [...]
Expected behavior
Configuration completes as with previous versions of Poco (although I expect Mumble will need other fixes too).
Please add relevant environment information:
Linux (GARStow)
POCO 1.14.0
CMake 3.31.1
Additional context
I've fixed this locally by adding cmake/FindUtf8Proc.cmake to the installation of FindPCRE2.cmake in CMakeLists.txt, and adding find_dependency(Utf8Proc REQUIRED) to cmake/PocoFoundationConfig.cmake; I'm not sure if that's the right fix, but it's consistent with how the other dependencies are handled.
The text was updated successfully, but these errors were encountered:
Describe the bug
Poco 1.14.0 introduced a dependency on Utf8Proc. However,
PocoFoundationConfig.cmake
doesn't have afind_dependency
call for it.To Reproduce
Install Poco 1.14.0 with
-DPOCO_UNBUNDLED
on Linux. Attempt to configure Mumble 1.5.634 against it (Mumble's CMake build system doesn't look for Utf8Proc itself). CMake fails, with the error:Expected behavior
Configuration completes as with previous versions of Poco (although I expect Mumble will need other fixes too).
Please add relevant environment information:
Additional context
I've fixed this locally by adding
cmake/FindUtf8Proc.cmake
to the installation ofFindPCRE2.cmake
inCMakeLists.txt
, and addingfind_dependency(Utf8Proc REQUIRED)
tocmake/PocoFoundationConfig.cmake
; I'm not sure if that's the right fix, but it's consistent with how the other dependencies are handled.The text was updated successfully, but these errors were encountered: