Hi Richard and other package maintainers,
after I posted this I realized that I had never got around to putting
the automated patching facility into the superbuild script. I have now
done this. If you wish to apply patches to either Hamlib or WSJT-X
sources when using the WSJT-X superbuild script to make a source package
or when building from a source package generated by the superbuild
script; you must make a suitable patch file for the package you wish to
patch and substitute it for one of the dummy patch files in the root of
the superbuild source tree (hamlib.patch or wsjtx.patch). The patch
differences must be relative to the pertinent source tree root
directory. The patch file(s) may be substituted before using the
superbuild script to generate a source package, in which case the
patch(es) will be injected for processing at build time, or the patch
file(s) may be substituted on the target build host after the source
tarball has been extracted.
For example the patch file I provided in the previous message should be
substituted for the empty file wsjtx.patch found a the root of the
superbuild source tree.
73
Bill
G4WJS.
On 26/10/2015 23:46, Bill Somerville wrote:
On 26/10/2015 23:14, Richard Shaw wrote:
Hi Richard,
On Mon, Oct 26, 2015 at 6:08 PM, Bill Somerville
<g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:
It is a newer Qt issue, they reorganized some header files and
v1.5 does
not build with QT >= 5.4. I had not worried about it since a v1.6.0
release is probably more likely than a v1.5.1 release.
If you really need to build V1.5 on FC22 then a bugfix release
could be
tagged.
I could just patch it if you have something handy.
Attached.
Thanks,
Richard
73
Bill
G4WJS.
------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
