On 26/09/2019 00:28, Barry Jackson wrote:
Hi Bill,
Just looking at 2.1.0 package for Mageia.
Getting this in the build log:
-- Checking for module 'hamlib'
-- Found hamlib, version 3.3
-- Found hamlib
CMake Error at
/usr/share/cmake/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/Modules/FindPackageHandleStandardArgs.cmake:378
(_FPHSA_FAILURE_MESSAGE)
CMake/Modules/Findhamlib.cmake:88 (find_package_handle_standard_args)
CMakeLists.txt:873 (find_package)
So...
Found HamLib....
Could not find Hamlib ??
Any Ideas.
It's a while since I looked at our wsjtx package and I remember that
hamlib was bundled with wsjtx at one time. Now it seems to be a
require, so should we be using a particular branch for our system
package?
Sorry I'm not up to speed but I have actually been playing radio and
building antennas rather than computing 24/7 :)
73
Barry
G4MKT
Hi Barry,
the official WSJT-X packages from the WSJT developers still include a
bundled Hamlib. If you have a package that relies on a separately
installed Hamlib package then you probably need to speak to the relevant
package maintainers. Note that the official CMake script for building
WSJT-X expects to statically link Hamlib, if your package uses that then
I would expect the Hamlib development package to be a prerequisite, the
runtime package with only headers and shared libraries would not be
sufficient.
The version of Hamlib linked to is not particularly critical so long as
it is recent, i.e. >= v3. The newer the Hamlib package linked, the more
up to date the supported radio list and bug fix status will be. WSJT-X
official packages are generally bundled with a snapshot of the Hamlib
master branch at the time of release.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
