On 03/03/2016 12:08, Barry Jackson wrote:
>> Once this issue is resolved there is another you need to address. For
>> >correct functionality you need to use a build of Hamlib from my fork or
>> >from the Hamlib 3.1 version (not yet released) as a minimum. This is not
>> >the cause of the errors you are seeing.
> Yes this is already catered for in our 1.6 build in the repos using the
> superbuild script to create our tarball but IIRC this does not work for
> snapshots.
>
Hi Barry,

you can make your own upstream tarball using the superbuild script, this 
can be built from any tag or branch HEAD. Although an arbitrary revision 
snapshot is not currently supported I would have thought that using a 
tag for stable released version or a branch HEAD for the latest & 
greatest should cover most requirements. If that is not so I could 
enhance the superbuild CMake script to build an upstream tarball from an 
svn revision. Another option is to use the patching capability of the 
superbuild script, both for WSJT-X and Hamlib it can automatically apply 
a patch set bundled in the upstream tarball it generates.

73
Bill
G4WJS.

------------------------------------------------------------------------------
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=272487151&iu=/4140
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to