Il 05/12/24 18:06, Black Michael ha scritto:
What do you mean "classic method" ?

Mike W9MDB


As I wrote in previous e-mail, I use the following syntax and I get the Hamlib included into the WSJT-X archive:


marco@linux-turion64:~/WSJT-X_build/build>
rm -rf /home/marco/WSJT-X_build/build/wsjtx-2.7.0/
tar -xzvf /home/marco/Scaricati/wsjtx-2.7.0-rc7.tgz -C 
/home/marco/WSJT-X_build/build/
cd /home/marco/WSJT-X_build/build/wsjtx-2.7.0/
 /usr/bin/cmake -Dhamlib_INCLUDE_DIRS=/usr/local/include \
 -Dhamlib_LIBRARIES=/usr/local/lib64/libhamlib.so \
 -Dhamlib_LIBRARY_DIRS=/usr/local/lib64 \
 -DWSJT_GENERATE_DOCS=OFF \
 -DWSJT_SKIP_MANPAGES=ON \
 -DWSJT_QMAP=NO \
 -Werror=deprecated-declarations \
 -Wno-error \
 -D CMAKE_INSTALL_PREFIX=/home/marco/WSJT-X_build/.wsjtx .
 (fresh build) /usr/bin/cmake --build .  --target install
 /usr/bin/cmake --build . --clean-first --target install


So, how can I use Hamlib GIT in my case?

73, Marco PY1ZRJ






On Thursday, December 5, 2024 at 02:22:16 PM CST, Marco Calistri via 
wsjt-devel<wsjt-devel@lists.sourceforge.net> wrote:






If I want to to build hamlib from GIT and keep using the classic method to 
compile WSJT-X, how to proceed?

Or better: how can I switch to hamlib GIT and ignore the hamlib version which 
comes with WSJT-X tar?

This is not yet clear to me!

Thanks for any guidance in this regard.

Regards,



---
73 de Marco, PY1ZRJ (former IK5BCU)


Attachment: OpenPGP_0x38215F3BB231677C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to