On 14/11/2018 21:11, Mark Klein wrote:
What CMake configure command did you you use for the first attempt
that you only show errors from in your OP?
cmake ..
cmake —build .
I’ve attached a bzip of the full build output up to the hamlib error.
I’m not up to speed on cmake, so I don’t know how it is doing its
dependency resolution, but it isn’t finding the local one provided in
the wsjtx tarball. My setting the property is to explicitly point to
the one built from the tarball, not the native one on CentOS7.
Hi Mark,
thanks for the info. I have a CentOS VM up now and am investigating why
the Hamlib package find is failing. We have a home brew CMake package
finder for Hamlib as no one has contributed the required CMake scripts
to ship with Hamlib. I really should sort that out and contribute
upstream ;)
CMake depedency resolution is basically driven by the "usual" system
library paths plus the CMake path variable CMAKE_PREFIX_PATH which can
override the "usual" paths, the latter is used in our packaged CMake
scripts and should be enough but clearly there is a problem on this
platform.
Your CMake configure line could include '-DWSJT_SKIP_MANPAGES=ON
-DWSJT_GENERATE_DOCS=OFF' which saves having to install many
dependencies not needed for the core application build.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
