Removed wsjtx dir again Build wsjtx rconfig There are two NOT_FOUNDs in the CmakeCache.txt CMAKE_SH:FILEPATH=CMAKE_SH-NOTFOUND hamlib_STATIC_LIBRARY:FILEPATH=hamlib_STATIC_LIBRARY-NOTFOUND
----------------------------------------------------------------- Configuring Release Build Tree For: ( wsjtx ) ----------------------------------------------------------------- -- The C compiler identification is GNU 4.8.0 -- The CXX compiler identification is GNU 4.8.0 -- The Fortran compiler identification is GNU -- Check for working C compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gcc.exe -- Check for working C compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gcc.exe -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/g++.exe -- Check for working CXX compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/g++.exe -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working Fortran compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gfortran.exe -- Check for working Fortran compiler: C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gfortran.exe -- works -- Detecting Fortran compiler ABI info -- Detecting Fortran compiler ABI info - done -- Checking whether C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gfortran.exe supports Fortran 90 -- Checking whether C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gfortran.exe supports Fortran 90 -- yes -- Detecting Fortran/C Interface -- Detecting Fortran/C Interface - Found GLOBAL and MODULE mangling -- Verifying Fortran/CXX Compiler Compatibility -- Verifying Fortran/CXX Compiler Compatibility - Success -- Found FFTW3: /JTSDK-QT/fftw3f/libfftw3f-3.dll -- Found PkgConfig: C:/JTSDK-QT/tools/pkg-config.exe (found version "0.28") -- checking for module 'hamlib' -- found hamlib, version 3.0~git -- Found hamlib -- Found hamlib: /JTSDK-QT/hamlib3/mingw32/include (Required is at least version "3") -- hamlib_INCLUDE_DIRS: /JTSDK-QT/hamlib3/mingw32/include -- hamlib_LIBRARY: /JTSDK-QT/hamlib3/mingw32/lib/libhamlib.dll.a -- hamlib_LIBRARIES: /JTSDK-QT/hamlib3/mingw32/lib/libhamlib.dll.a -- hamlib_STATIC_LIBRARY: hamlib_STATIC_LIBRARY-NOTFOUND -- hamlib_STATIC_LIBRARIES: -- Asking qmake for QT_PLUGINS_DIR and got C:/JTSDK-QT/qt5/5.2.1/mingw48_32/plugins -- Asking qmake for QT_IMPORTS_DIR and got C:/JTSDK-QT/qt5/5.2.1/mingw48_32/imports -- Asking qmake for QT_DATA_DIR and got C:/JTSDK-QT/qt5/5.2.1/mingw48_32 -- Configuring done -- Generating done -- Build files have been written to: C:/JTSDK-QT/wsjtx/build/Release ----------------------------------------------------------------- Finished Release Build Tree Configuration for: ( wsjtx ) ----------------------------------------------------------------- BASE BUILD CONFIGURATION Package ............ wsjtx Type ............... Release Build Directory .... C:\JTSDK-QT\wsjtx\build\Release Build Option List .. C:\JTSDK-QT\wsjtx\build\Release\CmakeCache.txt Target Directory ... C:\JTSDK-QT\wsjtx\install\Release LIST ALL BUILD CONFIG OPTIONS cat C:\JTSDK-QT\wsjtx\build\Release\CmakeCache.txt | less :: Arrow Up / Down to dcroll through the list :: Type (H) for help with search commands :: Type (Ctrl+C then Q) to exit TO BUILD INSTALL TARGET cd C:\JTSDK-QT\wsjtx\build\Release cmake --build . --target install TO BUILD WINDOWS NSIS INSTALLER cd C:\JTSDK-QT\wsjtx\build\Release cmake --build . --target package -----Original Message----- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Thursday, September 11, 2014 5:15 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Back in town 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 ------------------------------------------------------------------------------ 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
