On 11/09/2014 23:08, Michael Black wrote: Hi Mike, > OK...removed the wsjtx tree and "build wsjtx rconfig" > Still not found > What file is it looking for? OK, I need to see the output of the "build wsjtx rconfig" step please. > > And why does hamlib3 contain version 2 references? Not sure, probably because the Hamlib developers have not changed something yet, don't forget that Hamlib-3 is still pre-release. Whatever the reason it should not matter because we only use the static archive library version of Hamlib-3 which is in the JTSDK but not being picked up correctly in the configuration phase in your case.
<snip> 73 Bill G4WJS. > -----Original Message----- > From: Bill Somerville [mailto:g4...@classdesign.com] > Sent: Thursday, September 11, 2014 5:00 PM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Back in town > > On 11/09/2014 22:50, Michael Black wrote: > > <snip> >> //Path to a library. >> hamlib_STATIC_LIBRARY:FILEPATH=hamlib_STATIC_LIBRARY-NOTFOUND >> > <snip> > > The above line is the clue. I'm not sure why that is still showing as > -NOTFOUND. I think there may be a problem with the package finder I wrote > for Hamlib since *-NOTFOUND variables should be retried each build and once > the required package is in place should get populated. > > Can you try re-doing the whole configuration and generation phase of the > build. I'm not sure how to trigger that with the JTSDK. Deleting the > CMakeCache.txt file might help, if not try deleting the whole build tree and > re-running the build script. > > Summarizing, I think updating the JTSDK wasn't enough, you perhaps needed to > reconfigure and regenerate the build tree after that as well. > > 73 > Bill > G4WJS. > > ---------------------------------------------------------------------------- > -- > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce Perforce version control. > Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
