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
Is your feature request related to a problem? Please describe.
After installing activemq-cpp in vcpkg and doing find_package( activemq-cpp CONFIG ) I get the following warning:
1> [CMake] CMake Warning at XXXXX/vcpkg/scripts/buildsystems/vcpkg.cmake:834 (_find_package):
1> [CMake] Found package configuration file:
1> [CMake]
1> [CMake] XXXXX/vcpkg/installed/x64-windows/share/activemq-cpp/activemq-cppConfig.cmake
1> [CMake]
1> [CMake] but it set activemq-cpp_FOUND to FALSE so package "activemq-cpp" is
1> [CMake] considered to be NOT FOUND. Reason given by package:
1> [CMake]
1> [CMake] Activemq-cpp vcpkg install dependency failure: apr vcpkg port not found in
1> [CMake] XXXXX/vcpkg/installed/x64-windows.
1> [CMake] "XXXXX/vcpkg/installed/x64-windows/lib/libapr-1.dll"
1> [CMake] not found.
1> [CMake] "XXXXX/vcpkg/installed/x64-windows/debug/lib/libapr-1.dll"
1> [CMake] not found.
Proposed solution
The *.dll on Windows should be searched in the folder bin, not lib.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Cheney-W
changed the title
activemq-cpp to point to correct path for libapr-1.dll
[activemq-cpp] point to correct path for libapr-1.dll
May 25, 2023
Cheney-W
added
category:port-bug
The issue is with a library, which is something the port should already support
and removed
category:port-feature
The issue is with a library, which is requesting new capabilities that didn’t exist
labels
May 25, 2023
Is your feature request related to a problem? Please describe.
After installing activemq-cpp in vcpkg and doing
find_package( activemq-cpp CONFIG )
I get the following warning:Proposed solution
The *.dll on Windows should be searched in the folder bin, not lib.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: