On 26/11/15 12:47, Bill Somerville wrote:
On 26/11/2015 12:28, Barry Jackson wrote:

...
Regarding Hamlib, I would rather avoid any bundled software that is
available in the distro (it's also policy). I have been testing wsjtx
with our packaged hamlib and not had any problems that I am aware of, it
seems fine handling CAT with my TS-450S.
I have tested in both Mageia 5 (hamlib-1.2.15.3) and Mageia
6(dev)(hamlib-3.0).
What is the difference between your fork of hamlib (which I also tested)
and upstream hamlib? If there are major differences, and we were to
patch upstream with your changes, are they likely to adversely affect
other softwares that use hamlib?
This is a tricky area. First off there is no impact on other
applications as we statically link Hamlib into WSJT-X.

The background is that we found many issues with Hamlib despite it being
the best available library for CAT control and more. I forked Hamlib and
set about fixing the issues. WSJT-X should be built with a Hamlib from
my fork at present, it is hoped that we can switch back to a Hamlib
official package soon but we currently are still finding issues that are
not fixed in Hamlib 3.0 stable. I am pushing all my fixes upstream to
the Hamlib team so they are getting into their repo but there is still a
lag.

It is still strongly recommended to build with my Hamlib fork although
the differences with Hamlib 3.0 are currently minimal, nevertheless a
check with one rig is insufficient since the differences may only effect
other rigs. The upstream source tarball we provide which you can build
yourself (See ^/branches/wsjtx-superbuild for the project that does
that) contains the correct Hamlib fork sources to match the WSJT-X it
builds. Because of static linking, provision of an upstream source
tarball and my fork being in a public repository (github) there should
not be any packaging policy issues. Just think of it as more sources to
WSJT-X rather than a package dependency.

Thanks Bill,
I finally sorted it - but it's been a long night.
I think the INSTALL in wsjtx-superbuild dir could do with an update as I could not make sense of it for making the tarball.

I eventually experimented and wrote a little script to do the job.
One snag is that it includes CMakeCache.txt in the tarball which breaks things.

The script is attached for your interest and I will include it in our .src rpm to make my life easier in future ;)

I will put 1.6.0-rc1 in our repositories for the dev branch which is not due for release as Mageia 6 until next year, so that will give time for an update to the full release of wsjtx-1.6.0 as and when.

Many thanks for all your work on this project!

73
Barry
G4MKT


73
Barry
G4MKT
73
Bill
G4WJS.

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


#!/bin/bash
#
# This script creates the tarball for wsjtx which includes
# sources for a fork of hamlib which is statically linked
# during the build.
#
# Run in SOURCES after setting the required version tag.

name=wsjtx
version=1.6.0-rc1

[[ -e wsjtx-superbuild ]] && rm -rf wsjtx-superbuild

svn co svn://svn.code.sf.net/p/wsjt/wsjt/branches/wsjtx-superbuild

[[ -e $name-$version.tar.gz ]] && rm $name-$version.tar.gz

cd wsjtx-superbuild

cmake -D WSJTX_TAG=tags/$name-$version .

cmake --build . --target source

tar -xf $name-$version.tgz

rm -f $name-$version/CMakeCache.txt

tar -czf ../$name-$version.tar.gz $name-$version/

cd ..

rm -rf wsjtx-superbuild




------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to