On 20/10/2017 21:19, Ervin Hegedüs wrote:
$ cmake -D CMAKE_INSTALL_PREFIX=$HOME/wsjt -D hamlib_LIBRARY_DIRS=$HOME/hamlib-prefix Qt5Widgets_DIR=/usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets Qt5Multimedia_DIRQt5Multimedia_DIR=/usr/lib/x86_64-linux-gnu/cmake/Qt5Multimedia .

Hi Ervin,

this is not the preferred way to configure the WSJT-X CMake build. The Qt libraries will be found automatically as they are installed in the "usual" place. The only library you need to help CMake to find is the Hamlib fork you have built, to do that you only need to provide the path to your local Hamlib install via the CMAKE_PREFIX_PATH variable. Something like:

$ cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix .

You may also wish to set other optional variables to skip building the User Guide or manpages, they need several packages to be installed and it is much quicker to skip them if you only want the executables.

Note that CMake will not change fundamental configuration variables when re-running so you will have to scrap your build tree and re-configure to switch to the Hamlib local install properly.

The reason for the Hamlib fork is that we contribute a lot of patches to the Hamlib project and the fork is tracking the Hamlib master branch and sometimes ahead of it while patches flow upstream to the Hamlib team. Until Hamlib v3.1 at least is in the distro packages the fork is the best version to use.

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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to