On Tue, Oct 27, 2015 at 11:13 AM, Joe Taylor <[email protected]> wrote:
> Hi Bill, Richard, and all, > > I guess we need to decide whether there will be a v1.5.1 release. As > Bill suggested, an alternative is to offer a v1.6.0-rc1. > > If we do a v1.5.1 release, it would be well to include the corrected > version of jt65code committed (to v1.6.0) in SVN revision 6000. Sounds good to me. Also, while you're at it I have some improvement ideas for the superbuild script: https://dl.dropboxusercontent.com/u/34775202/wsjt/wsjtx-1.5-qt54.patch 1. The change from ${MAKE_EXECUTABLE} to $(MAKE) The probably obsoletes the need to find make, also, it passes the current instance of make to the external project so SMP flags work (-jX) 2. I removed the LOG options from the external projects because it was redirecting (not tee'ing) into a file which means the resultant build.log from rpmbuild did not have the verbose build info and had to be extracted from the internal cmake logs. Further, it separates the stdout and stderr which makes it impossible to see the error inline for proper context. 3. I had to add V=1 for hamlib to get verbose output during build (automake equivalent to VERBOSE=1) to check build flags. 4. I had to force -fPIC for the hamlib build. I assume this is a bug in it's configure because both gcc and g++ are checked for PIC compatibility but only the c++ files are compiled with -fPIC. Obviously you can ignore the patch line as that was my workaround for the qt 5.4 issue. Thanks, Richard
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
