Hello All,
Over the last couple months I've been compiling a list of issues
reported by users from various forums, mailing lists and blogs. I
believe I have most of the major issues corrected. There is still some
tidy-up work to be done on documentation, fix typo's and such, however,
all the modes I am able to test seem to work as expected. Bare in mind,
these changes *have not been formally released by Joe*, so, use / test
your own risk.
I've tested both applications for basic functionality on Ubuntu 14.04
i386, amd64 and Ubuntu Mate 15.10 amrv7. JTSDK-Nix v2.0.19, when
released, will be updated to allow for the changes made below.
[1] WSJT / WSPR - On systems with both Python2-Numpy and Python3-Numpy,
the F2PY m4 search macro was finding Python2-Numpy first rather than
Python3-Numpy which manifests itself as a PyObject error. I believe this
is now resolved.
[2] WSJT / WSPR - In the past, finding portaudio headers and libraries
was problematic, particularly on FreeBSD and OSX for various reasons.
Fixes that were added to WSPR have now been ported to the WSJT autotools
scripts. You should not have to pass the portaudio locations using
AC_ARG_ENABLE. If this is still a problem, please advise.
[3] WSJT / WSPR - due to non-standard install locations, and the need to
have various files in the run directory, packaging and running multiple
instances of the applications was either impractical or required copying
the entire package to a local $USER owned location. With the new install
locations + a shell wrapper script, I believe this is now resolved.
There is one catch to this; WSJT and WSJT-X share two files with common
names ( jt65code and jt4code ). This would cause problems (overwriting)
for both the binaries and their manpages if they were both allowed to be
installed to --prefix=/usr. It is for this reason, when installing WSJT
from source code, users should leave the current prefix as stated in the
configure script: --prefix=/usr/local/wsjt/{bin,lib,share}. If you must
change this location, consider using --prefix=/opt or some other
non-system location.
[4] WSJT / WSPR - For the reasons stated above, users did no have an
easy method of running multiple instances on the same machine without
creating multiple copies of the full installation. This made keeping
track of system package updates more difficult. Users can now run
multiple instances of either WSJT or WSPR using a similar method as
WSJT-X currently employs; wsjt -[-n NAME] [-p PATH], the same for WSPR.
Both operators are optional, if you call the script without either
switch, the application runs from ~/.local/share/[APP-NAME].
[5] WSJT / WSPR - Documentation and Manpage builds require a substantial
number of packages to be installed in order to complete the full build.
Both WSJT and WSPR now have switches the user can enable to turn off
Docs and Manpage builds. To disable them, run:
./autogen.sh --disable-docs --disable-manpages
Both Docs and manpages are *enabled by default*. This may change in the
future.
[6] WSJT / WSPR - Both packages now employ the same build method:
./autogen.sh [OPTIONS]
make
sudo make install
For a short list of application specific options, use:
./autogen.sh
./configure --help=short
[7] WSPR - Originally, the list of available rig was from a static rig
file which required a package update to change the list. The shell
script now generates this list each time it is run. If Hamlib is updated
in your distribution, the rig list in WSPR should also be updated. This
feature requires the binary rigctl, provided by most libhamlib-utils
packages. This opens the door for users to compile their own copy of
Hamlib, adding rigctl to one of the ^/bin locations in the $PATH.
That covers the major changes, but there were / are many smaller times
that should not pose problems for end users building from source. If
anyone has issues, feedback, improvement ideas, whatever, you can send
them to the dev-list or email me off-line if you prefer.
73's
Greg, KI7MT
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
