Open PatrickKa opened 5 months ago
Vcpkg port bug. Instead of a proper CMake config, the port installs an improper vcpkg cmake "wrapper".
For now, you might get away with find_package(PLIBSYS REQUIRED)
.
Thx for the fast answer.
Yeah, this is what I am using in my package config file for now.
Describe the bug
The documentation of
find_package()
states that it sets<PackageName>_FOUND
. However, after I callfind_package(plibsys CONFIG REQUIRED)
in my CML file,plibsys_FOUND
is not set. I am not sure if this bug is directly related to vcpkg, but when I wanted to check the CMake config file in.../vcpkg/installed/x64-windows/share/plibsys
I only foundvcpkg-cmake-wrapper.cmake
which manually setsPLIBSYS_INCLUDE_DIRS
andPLIBSYS_LIBRARIES
. Therefore, I thought that this wrapper might also be responsible for manually settingplibsys_FOUND
.The way how I discovered this was via
find_dependency(plibsys)
in a CMake config file of "MyCMakeProject", which throws an error stating that it cannot find plibsys which is very weird becausefind_package(plibsys CONFIG REQUIRED)
does not throw an error and building "MyCMakeProject" works.Environment
To Reproduce
Steps to reproduce the behavior:
find_package(plibsys CONFIG REQUIRED)
and print the value ofplibsys_FOUND
afterwards.Repro code:
Expected behavior
plibsys_FOUND
is set to 0 or 1 after thefind_package()
callFailure logs
Additional context Add any other context about the problem here.