As two alternatives to self building for the latest and greatest: if you're on Raspi OS 12 (bookworm) 64 bit, you can enable debian backports [1] and install a pretty up to date copy of wsjtx.
If you're not on bookworm 64bit, I maintain a private repo called hibbian [2] in which I maintian and backport a number of things both from my work in Debian [3] and privately, one of which is the most up to date wjstx suite across x86_64, i386, armhf (32bit raspi, v2 hardware onwards) and arm64 (64bit raspi, v3 hardware onwards). I cover Trixie (testing), bookworm (stable) and bullseye (oldstable) where possible, although I've not yet backported the latest wsjtx to bullseye as I need to do hamlib first, and that has breaking changes to some other packages. [1] https://backports.debian.org/Instructions/ [2] https://www.hibbian.org/ [3] https://qa.debian.org/developer.php?login=hibby&comaint=yes -- Dave Hibberd <hi...@debian.org> Debian Developer Packet Radioist MM0RFN On Tue, 26 Nov 2024, at 11:32 AM, Marco Calistri via wsjt-devel wrote: > Hi MIke! > > I use the following procedure to compile WSJT-X on my Linux: > > 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 > > I do not compile Hamlib from GIT and it seems I'm fine, but I would like to > ask you: > > By using the above procedure, I'm going to use the latest Hamlib along with > my WSJT-X compiling? > > In case I would like to try the GIT procedure you indicated for Hamlib, are > there any instructions I need to change, in order to compile WSJT-X as I do > every time? > > Many thanks and best regards! > > Note: I've not heard anymore about source language translations, I don't know > if I missed something. > > --- > *73 de Marco, PY1ZRJ (former IK5BCU)* ** > > > Il 25/11/24 10:32, Black Michael via wsjt-devel ha scritto: >> That information is out-of-date >> >> $ mkdir ~/hamlib-prefix >> $ cd ~/hamlib-prefix >> $ git clone https://github.com/Hamlib/Hamlib src >> $ cd src >> $ ./bootstrap >> $ mkdir ../build >> $ cd ../build >> $ ../src/configure --prefix=$HOME/hamlib-prefix \ >> --without-cxx-binding --disable-winradio \ >> CFLAGS="-g -O2" \ >> LDFLAGS="-Wl" >> $ make >> $ make install-strip >> >> Mike W9MDB >> >> >> >> >> >> >> >> >> On Monday, November 25, 2024 at 07:12:31 AM CST, mark--- via wsjt-devel >> <wsjt-devel@lists.sourceforge.net> wrote: >> >> >> >> >> >> >> I am building on a Raspberry Pi. >> >> INSTALL file says clone Hamlib and checkout “integration” branch. >> I cannot find integration branch, or any mention of it on Hamlib repo. >> Am I missing something? >> >> Mark >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> > > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > *Attachments:* > • OpenPGP_0x38215F3BB231677C.asc > • OpenPGP_signature.asc
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
