On 21/10/2017 22:15, Ervin Hegedüs wrote:
But when I pass the system installed Hamlib path:
-- Checking for module 'hamlib'
-- Found hamlib, version 3.1
-- Found hamlib
CMake Error at
/usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least
version "3")
Call Stack (most recent call first):
/usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:377
(_FPHSA_FAILURE_MESSAGE)
CMake/Modules/Findhamlib.cmake:81 (find_package_handle_standard_args)
CMakeLists.txt:735 (find_package)
-- Configuring incomplete, errors occurred!
But when I pass the hamlib_* environment variables (from the
first output), eg: -D hamlib_INCLUDE_DIRS="/usr/include/...libusb-2.0",
then all code has built as well, including rigctl binaries.
What should I do for leave these variables, and cmake recognize
all necessary lib and headers?
Hi Ervin,
I need to do some work to ensure that CMake detection of Hamlib works
correctly for system installed Hamlib libraries. This has only become
possible with the very latest distributions that are starting to include
Hamlib v3.1. For now I suggest building with my Hamlib fork. When I have
made the changes there should be no need to pass any paths nor set
environment variables for CMake to locate Hamlib, I believe I set the
current CMake scripts to break with the system Hamlib because of many
issues with WSJT-X using v2 Hamlib versions.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
