Bill, * that Debian package was targeted at Ubuntu 18.04, … Yet you clearly stated that there are no issues with 20.04 … I am confused … and so are countless others emailing me !
The Qt5 packages are NOT NATIVELY delivered in Ubuntu and many other Linux distros as they are large and volatile. I started with 18.04.4 “oob”…. My pedigree with Linux is such that I am an early Kernel Developer (via an early “handle”) … and I am one that that has built OS’s from scratch using Andy Tannenbaum’s guides … I can foresee from many of your answers here that you start with systems that already have build-environ deployed … Most people do not ! I get queries and cries for help from people that cannot get it to work ON ENVIRONS that you certify as working. So, deploying the build environ (i.e. the JTSDK @ GROUPS.IO work) is basically essential for many using Linux / Unix-based environ anyway ! I’ll be blunt – your Linux .deb installers MUST pull in dependency packages. They currently do not (so additional scripting work is needed) …. Solving these issues as you know basically is easier suggesting compiling from scratch …. * Again I ask to please do not obfuscate the process of building WSJT-X from the combined sources tarball… Obfuscate? Obfusacate? The last response contradicts in responses !!! I am just repeating, trying to clarify, make sense of for others materials and in many cases correct instructions that are ALMOST EXACTLY WHAT YOU HAVE IN YOUR INSTALL FILES … INSTALL FILES IN TWO LOCATIONS THAT ARE OUT OF DATE IN PLACES THAT HAVE CONTRADICTIONS. [ And yes some of my posts refer to the Development streams of Hamlib … as using these makes WSJTX works soooooo much better for many as their rigs work when “corrected” Hamlib source is used ]. If I was to use steps documented inside the wsjtx.tar tarball inside the INSTALL file steps will not compile as it lacks the MANPAGE switches. This is EXACTLY the same issue that I am raising if I was to use the .deb files distributed on Joe’s site ! i.e. Things do not work well and properly ! Please review these KEY FILES – as I have been requesting - to stop OBFUSCATING PROCESSS for those trying to learn and those thata re not as skilled. Aim to improve the skills of others (and that is where I come from). I am more than happy to correct files myself - if they have not already been corrected. Yet that last point is a key issue. With the development process CLOSED I (or others) do not know whether issues have been fixed. Others also willing to contribute also do not know whether their efforts are in vain either ! I never get a straight answer from you as to whether some of these issues have been fixed !!!!! You cannot have your cake and eat it too as I say often. Let’s leave this discussion here as I think you are massively entrenched. But for The Great Maker’s sake, realise people do not comment here unless they have to as they fear ridicule and retribution ! Newbies also are attracted here … Listen and at least acknowledge the contribution from vast numbers of people that do suggest; always treat newbies with the respect that they deserve. Regards to all in the WSJTX and Hamlib community. Steve I VK3VM / VK3SIR Maintainer of Patches that make JTSDK 3.1 work ! On 14/08/2020 15:50, Stephen VK3SIR wrote: Bill, I am off the sick list again…… Ok I am going to put my “Newbie” hat on here (as this is the type of help request that I get by PM). * One deploys Ubuntu 20.04.1 using the software at https://ubuntu.com/download/desktop * You perform the obligatory OS update once its installed. * You download https://physics.princeton.edu/pulsar/K1JT/wsjtx_2.2.2_amd64.deb * You ATTEMPT to install it with “Software Installer” … It responds with ‘Unable to Install “Message Aggregator”: The following packages have unmet dependencies:’ without further information. I have just re-confirmed this in a virgin (but fully updated) Ubuntu 20.04.1 x64 VM …. [ Now both you and I can fix this in our sleep – but resolving this is difficult for many in our community…. So they come to people like you and me and this forum for help ] A “newbie” just expects these things to work OOB … That was the whole gist of my points the other day. I don’t point-score as that helps nobody ! BY FAR the best and easiest way to get a system working is to compile it from scratch; Instructions for this (including a comment re your “official” way) are on the JTSDK @ GROUPS.IO forum… That way people learn to solve their own issues … and the more that you can promote learning the less “annoying comments” as some may call them appear here. There is an old-ancient proverb: give a man a fish and you feed him for a day; teach a man to fish and you feed him for a lifetime. HAM – Help All mankind. 73 Steve I VK3VM / VK3SIR From: Bill Somerville <g4...@classdesign.com><mailto:g4...@classdesign.com> Sent: Wednesday, 12 August 2020 10:30 AM To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2 tarball Steve, your reply below makes no sense! I will repeat, the combined sources tarball we release includes instructions to build on Linux, they are complete. Yes there are some typos and it needs updating for the version numbers mentioned, that is fixed for the next release, did you even read this email thread before suggesting that some other instructions should be followed? What are you suggesting needs to be "forced" to run? By far the simplest instructions to follow are the ones provided in the single INSTALL file at the root of the sources tarball. Note the singular INSTALL file. Like many Open Source projects there are different build instructions for developers wishing to contribute to the project, there's nothing unusual about that, but those instructions are not needed for users who simply want to build the application to run. We provide a build script, and instructions to run it, just for that sort of user. 73 Bill G4WJS. On 12/08/2020 01:21, Stephen VK3SIR wrote: Bill, KISS Principle in my answer to Rob’s post …. Yes the “dropped tarball” it can be forced to run … but its BY FAR simpler and easier to follow the instructions in the INSTALL files :-D I have had lots and lots and lots of background inquiry on Ubuntu 20.04 … following the steps in the install file and compiling from source is BY FAR the easiest way to make WSJTX work – and properly (considering there have also been a lot of changes to Hamlib). By the way, has the INSTALL files been updated for the next release as they were a little dated and some instructions out of sync? 73 Steve I VK3VM / VK3SIR From: Bill Somerville <g4...@classdesign.com><mailto:g4...@classdesign.com> Sent: Wednesday, 12 August 2020 10:10 AM To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2 tarball Steve, there is no need to follow the build instructions in the project git repo if you are building to run. Maybe if you are building to contribute patches. The INSTALL file in the sources tarball we provide contains complete instructions for building a working WSJT-X for Linux. Please don't over-complicate a relatively simple recipe for building. 73 Bill G4WJS. On 12/08/2020 01:01, Stephen VK3SIR wrote: Rob, There is no repo that you can just “drop and run” for WSJTX 2.2.2 – You really need to compile your own !!!! Go to the JTSDK @ GROUPS.IO site. I have a post there for dependencies etc. needed to build your own WSJTX on Ubuntu 20.04. i.e. https://groups.io/g/JTSDK/topic/some_dependencies_requisites/75311015?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,75311015 Then follow the steps inside the INSTALL files (the top level one in the repo and then the main set of steps inside WSJTX.TGZ) 73 Steve I VK3VM / VK3SIR From: Rob Robinett <r...@robinett.us><mailto:r...@robinett.us> Sent: Wednesday, 12 August 2020 8:44 AM To: WSJT software development <wsjt-devel@lists.sourceforge.net><mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Changes to the INSTALL file in the 2.2.2 tarball 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 https://lists.sourceforge.net/lists/listinfo/wsjt-devel
