Hello All, Just thought I'd pass this along.
After Bill updated the upstream autogen.sh script, and I moved the JTSDK Hamlib3 Source & Build locations outside of MSYS $HOME directory ( C:\JTSDK\src\hamlib3\.. .. ), Jay was able to build Hamlib without error. Both the Hamlib and JTSDK-DOC build issues have been resolved. 73's Greg, KI7MT On 6/25/2015 3:58 AM, Bill Somerville wrote: > On 25/06/2015 10:51, KI7MT wrote: >> Hi Bill, > Hi Greg, > > ... > >>> I can fix that, there are a few other related changes needed. That will >>> at least allow autogen.sh to run but here are deeper issues with >>> configure itself. The configure script is going to barf if $SRCDIR or >>> `pwd` have whitespace in them and I don't think that can be resolved. >>> >>> Unless you can get the JTSDK to install the sources and use a build >>> directory that are outside of the users %HOMEDIR% I believe this may be >>> a futile effort. >> Thats a good idea actually. I didn't think about moving the source out >> of $HOME. I would think the logical location would be along side the >> other source folders: c:/JTSDK/src/hamlib3 or similar. That should take >> $USER out of the path completely. >> >> At present, all I'm doing is a git pull from within $HOME, but I don't >> see any reason it should not work from another non-white-space location >> as we're using the Qt5 Tool chain already, which is outside of the >> ../msys paths anyway. Rather than cd $HOME, just cd to the JTSDK/src >> folder then do the pull / integration checkout. >> >> I'll look at that later today. It should not require much of a change to >> implement. >> >>> I will submit the autogen.sh patches so at least it runs but configure >>> will exit with an error about unsafe characters in $SRCDIR, which is >>> probably correct. > I have fixed autogen.sh in my integration branch and pushed a patch > upstream to the Hamlib developers. > > ... > > 73 > Bill > G4WJS. ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
