Hello All,
I finished updating JTSDK-Nix for the restructured repository, or at least,
to extent it can be updated without a significant undertaking. Before 105's
start flying, a couple of things need to be understood. First, JTSDK-Nix
never had the same build capabilities as JTSDK-Win32. It does not build all
branches, tags, and trunk locations. Never has, and probably never will
unless somebody picks it up. Second, IMHO, it would be more efficient to
start from scratch rather than trying to piece together methods to
accommodate all primary build locations in the repository. Finally, like
JTSDK-Win32, unless there are build-breaking items in this release, I do not
plan to continue working the project for the reasons explained in previous
posts.
UPGRADING:
"Before" you run JTSDK-Nix (after the upgrade), it is highly advisable to
rename the following folders:
* Copy or Move /home/$USER/jtsdk/src to /home/$USER/jtsdk/src.bak (or
whatever you like)
* Copy or Move /home/$USER/jtsdk/wsjtx to /home/$USER/jtsdk/wsjtx.bak
(or whatever you like)
If there are any build path or checkout bugs, moving / backing up your
original code ensures it will be as it was before the upgrade.
CURRENT CAPABILITIES:
I only tested a few builds. I did not test all available options. For
WSJT-X, the 1.9.0 tag was tested. The same was true for the WSJT-X
Superbuild.
WSJT:
Only builds ^/wsjt/trunk. This is nothing new and has always been. The
source code is just in a different location.
WSPR:
Same as WSJT, it only builds the trunk ^/wspr/trunk. And again, this has not
changed. Only the location of the trunk changed.
WSJTX-Superbuild:
I don't have a use-case for this script, and rarely use it; others may so I
updated it. The jtsdk-wsjtx-superbuild script only builds from branches
^/wsjtx/branches and tags ^/wsjtx/tags. I tested the build for Tags 1.9.0,
and that was all. Manually using the superbuild script, I believe you can
build what you like. However, I've not looked at it closely in some time,
things may have changed.
WSJT-X:
Originally, WSJT-X built from its trunk which was under ^/branches/wsjtx,
that is no longer the case. The WSJT-X build script is like wsjtx-sb,
insofar as, it only builds ^/wsjtx/branches and tags ^/wsjtx/tags.
Hamlib:
Until something changes in that source repository, it should be ok. For how
long, I do not know. What I do know is, the JTSDK-Nix Hamlib build script
is not very flexible. Any change will likely break the app builds that
depend on Hamlib being custom built (if using JTSDK Build Scripts that is).
Or at the very least, fail to checkout and build. If all else fails, there's
always the command-line. Instructions are in the SF repository for WSJT-X I
believe.
PACKAGING and SOURCE CODE:
Launchpad PPA:
https://launchpad.net/~ki7mt/+archive/ubuntu/jtsdk
Source Code:
https://github.com/KI7MT/jtsdk-nix/releases/tag/jtsdk-nix-2.0.26
73's
Greg, KI7MT
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
