Describe the bug
The generated cmake build files have hardcoded paths in them(which does not work with vcpkg). This causes vcpkg to both emit a warning, and any applications that attempt to use libosdp to fail.
Due to how the cmake package files are generated as well, the way to link is not standard compared to other cmake libaries(e.g. there is no libosdp::osdp target to link to).
Expected behavior
The library is able to be built and used with vcpkg.
Observed behavior
vcpkg complains about hardcoded paths, and the final link of any application that tries to use libosdp does not work.
Additional context
This happens on both Linux and Mac.
Describe the bug The generated cmake build files have hardcoded paths in them(which does not work with vcpkg). This causes vcpkg to both emit a warning, and any applications that attempt to use libosdp to fail.
Due to how the cmake package files are generated as well, the way to link is not standard compared to other cmake libaries(e.g. there is no libosdp::osdp target to link to).
Expected behavior The library is able to be built and used with vcpkg.
Observed behavior vcpkg complains about hardcoded paths, and the final link of any application that tries to use libosdp does not work.
Additional context This happens on both Linux and Mac.