OK...removed the wsjtx tree and "build wsjtx rconfig" Still not found What file is it looking for?
And why does hamlib3 contain version 2 references? C:\JTSDK-QT>more hamlib3\mingw32\lib\libhamlib.la # libhamlib.la - a libtool library file # Generated by libtool (GNU libtool) 2.4.2 Debian-2.4.2-1ubuntu1 # # Please DO NOT delete this file! # It is necessary for linking the library. # The name that we can dlopen(3). dlname='../bin/libhamlib-2.dll' # Names of this library. library_names='libhamlib.dll.a' # The name of the static archive. old_library='' # Linker flags that can not go in dependency_libs. inherited_linker_flags='' # Libraries that this one depends upon. dependency_libs=' -lws2_32' # Names of additional weak libraries provided by this library weak_library_names='' # Version information for libhamlib. current=3 age=1 revision=0 # Is this an already installed library? installed=yes # Should we warn about portability when linking against -modules? shouldnotlink=no # Files to dlopen/dlpreopen dlopen='' dlpreopen='' # Directory that this library needs to be installed in: libdir='/c/test-install/hamlib/mingw32/lib' -----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
