Rob,
I don't understand your question, there is only one WSJT-X sources
tarball for v2.2.2, it should build on any Linux system that has Qt v5.5
or newer on it. What wheel do you think you are trying to re-invent?
If you have an error message from trying to build WSJT-X from sources
then tell us what it is and we can help.
73
Bill
G4WJS.
On 11/08/2020 23:44, Rob Robinett wrote:
Hi Bill and David,
Could I find a source tarball which builds on Ubuntu 20.04? I have
several wsprdaemon sites which want to move to 20.02.
My attempt to follow David's instructions have failed and I have so
much other SW to work on that I don't want to reinvent the wheel.
Thanks,
Rob
On Mon, Aug 3, 2020 at 4:55 AM Bill Somerville <g4...@classdesign.com
<mailto:g4...@classdesign.com>> wrote:
Hi David,
I am not ruling out portable packaging, I just don't think it
should be the prime focus of a small and busy development team. If
someone makes a portable package, commit to keep it up to date,
and it gets some traction amongst Linux users of WSJT-X; then
that's fine.
I assume you realize that the WSJT-X CMake build script already
knows how to make a basic Debian or RPM package, the package
target does that if run on a suitable machine. You would be better
to use a git checkout rather than the combined WSJT-X sources
tarball with bundled Hamlib. That would mean separately installing
Hamlib, which is not hard and the WSJT-X repo INSTALL file
(different from the one in the combined sources tarball) has a
recipe. Making a package is no more than invoking `make package`
or `cmake --build --target package`.
73
Bill
G4WJS.
On 03/08/2020 08:48, David Spoelstra wrote:
Bill-
Just got a new wsjt digest where you answered a question about
Flatpak. From your answer, that doesn't seem to be the correct
direction.
Since I like to be on the latest distro of Ubuntu, maybe I should
learn to make a deb and give you guys that to post?
Basically I'm looking for some pointers on how to best help the
project.
73,
-David, N9KT
On Sun, Aug 2, 2020 at 4:38 PM David Spoelstra
<dav...@mediamachine.com <mailto:dav...@mediamachine.com>> wrote:
Bill-
I just built 2.2.2 on Ubuntu 20.04 and noticed a few things
that should be fixed in the INSTALL file in the 2.2.2
tarball. Some of them are cosmetic. Some are actual errors if
you follow the steps (line 131). Just my way to try and help
the project!
Line 13:
Copyright 2001 - 2018 by Joe Taylor, K1JT.
should be:
Copyright 2001 - 2020 by Joe Taylor, K1JT.
Line 34 (Debian name):
Also qtmultimedia5-dev, libqt5libserialport5-dev,
qttools5-dev,
should be:
Also qtmultimedia5-dev, libqt5serialport5-dev, qttools5-dev,
Line 35 (Debian name):
libusb-1.0.0-dev
should be:
libusb-1.0-0-dev
Line 71:
repository e.g. wsjtx-1.9.1 by specifying it as a
variable to
should be:
repository e.g. wsjtx-2.2.2 by specifying it as a
variable to
Line 74:
$ cmake -D WSJTX_TAG=wsjtx-2.0.0 <source-dir-path>
should be:
$ cmake -D WSJTX_TAG=wsjtx-2.2.2 <source-dir-path>
Line 111:
$ cmake -D WSJTX_TAG=wsjtx-2.0.0 <source-dir-path>
should be:
$ cmake -D WSJTX_TAG=wsjtx-2.2.2 <source-dir-path>
Line 122:
The above commands, if successful, will produce
'wsjtx-1.9.1.tgz'
should be:
The above commands, if successful, will produce
'wsjtx-2.2.2.tgz'
Line 128:
$ tar xzf wsjtx-2.0.0.tgz
should be:
$ tar xzf wsjtx-2.2.2.tgz
Line 131:
$ cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF
../wsjtx-2.0.0
should be:
$ cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF ..
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Rob Robinett
AI6VN
r...@robinett.us <mailto:r...@robinett.us>
mobile: +1 650 218 8896
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
