Stephen,
we have never advised those that build WSJT-X from sources to use
anything other than my Hamlib fork since WSJT-X v1.4, either the
integration branch HEAD or the tag associated with the WSJT-X release
being built is recommended. My fork is kept up to date with the Hamlib
official master branch. Note that the tags in my fork are important
since they reference the exact Hamlib code base used with official
WSJT-X builds.
WSJT-X v2.2.0 will be compatible with Qt versions 5.5 through to 5.14.2,
although the last time I checked Qt 5.13 has a defect that makes it
unusable with WSJT-X. Officially only Qt v5.7 through v15.14.2 are
supported from WSJT-X v2.2.0 but we know a few older and somewhat
obsolete Linux distribution versions still ship with Qt 5.5.
WSJT-X is FOSS using a GPLv3 licence so of course the sources will be
placed in the public domain at the point of release of a public beta
test release candidate. As always the sources will be in our SourceForge
git repository and in an "upstream" sources tarball designed for Linux
packagers, including the CMake build script to build both Hamlib and WSJT-X.
73
Bill
G4WJS.
On 10/05/2020 20:14, Stephen Ireland wrote:
Hi Bill,
Thanks for that tip !
I had been advised that you had merged your fork of Hamlib back into
the main fold – with suggestions that only the official Hamlib
releases should be used for WSJT-X code – hence scripts with the
“experimental code” for making JTSDK 3.0 (x86 compile) and 3.1 (x64
compile) work documented at “jt...@groups.io <mailto:jt...@groups.io>”
(Google that to find the address) were set that way !
I have noted that Mike W9MDB has achieved some amazing things of late
with the mater releases of HAMLIB – in particular having it
compiler-error free without turning compiler switches off … This is
almost unheard of in terms of any software development (so well done
Mike) !!!!
Firstly, will source be released with the 2.2.0 rc1 candidate proposed
to be released sometime today?
Secondly and important if source is proposed to be released, can you
please offer some guidance now pre-release for the excited community
that work with the JTSDK with regards to preferred CMAKE, FFTW, Qt
etc. versions? As we know there are some differences between Qt
versions and facilities that they offer and deprecate !
[ I would assume that Qt would be “set” at the latest LTS (3 year
support) version being Qt 5.12.8 … although the “experiment” scripts
that I have shared demonstrate how to set to and fall back to Qt
5.14.2 (the latest release) as default. ]
73 and thanks,
Steve I
VK3VM / VK3SIR
*From:*Bill Somerville <g4...@classdesign.com>
*Sent:* Sunday, 10 May 2020 7:59 PM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Coming soon: WSJT-X 2.2.0-rc1
On 10/05/2020 10:51, Claude Frantz wrote:
On 5/5/20 6:17 PM, Joe Taylor wrote:
This message is to let you know of some important WSJT-X
development plans. We plan to make a first candidate release
of WSJT-X 2.2.0 next Monday, May 10.
WSJT-X 2.2.0-rc1 will be a beta-quality release candidate
providing a number of new features and capabilities.
Hi Bill & all,
Which releases of hamlib can be used to compile ?
Is the use of the special wsjt style hamlib mandatory ? What are
the differences vs. "standard" hamlib ?
Best wishes,
Claude (DJ0OT)
Hi Claude,
although it is still recommended to use my fork of Hamlib, currently
my fork integration branch is the same as its master branch which in
turn is close to the current Hamlib master branch at commit 320b2552.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
