On 11/09/2014 21:31, Michael Black wrote: Hi Mike, > I reinstalled JTSDK-QT and that cleared up the DLLs in the Release\bin > directory. > I think I had put the DLLs in there myself since I run WSJT-X on a different > computer than I build on. OK, that is a side effect of a deeper error. > > But when I did "build wsjxt rinstall" and then say yes to "Run wsjtx Now?" I > get hamlib-2.dll is missing (might be why I copied it before). > I've got both a hamlib and hamlib3 directory but I don't see where the > hamlib dir is referenced in the cache so not sure where it's picking up > version 2. So is that. > And I just noticed this error during the build now. > CMake Error at cmake_install.cmake:71 (FILE): > file INSTALL cannot find "C:/JTSDK-QT/src/wsjtx/RIGCTLD_EXE-NOTFOUND". And that. > I removed the wsjtx subdir and rebuilt again and got the same problem. It's > not finding rigctld.exe > I assume it should be grabbing the one residing in here...but there's > libhamlib-2.dll again!!!! > Directory of C:\JTSDK-QT\hamlib3\mingw32\bin > > 03/27/2014 10:35 AM <DIR> . > 03/27/2014 10:35 AM <DIR> .. > 03/27/2014 11:36 AM 7,089,621 libhamlib-2.dll > 03/27/2014 11:36 AM 302,018 rigctl.exe > 03/27/2014 11:36 AM 322,872 rigctld.exe > 03/27/2014 11:36 AM 185,014 rigmem.exe > 03/27/2014 11:36 AM 114,264 rigsmtr.exe > 03/27/2014 11:36 AM 111,344 rigswr.exe > 03/27/2014 11:36 AM 165,493 rotctl.exe > 03/27/2014 11:36 AM 187,900 rotctld.exe The line:
//pkg-config executable PKG_CONFIG_EXECUTABLE:FILEPATH=PKG_CONFIG_EXECUTABLE-NOTFOUND in the following CMakeCache.txt is the culprit. The WSJT-X CMake build requires the PkgConfig tool to correctly locate and enumerate the Hamlib library. Greg Ki7MT recently updated JTSDK to fix this issue but it appears you are still not getting PkgConfig on your PATH during the build. Are you certain you have followed all the instructions to install the latest JTSDK? Maybe Greg can chip in with a hint as to why this is not working. <snip> > -----Original Message----- > From: Bill Somerville [mailto:g4...@classdesign.com] > Sent: Thursday, September 11, 2014 2:27 PM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Back in town > > On 11/09/2014 20:04, Michael Black wrote: > Hi Mike, >> When is hamlib-3 used? At least for my build on Windows 7 hamlib2 is >> what is used and ends up in the install. > If you are using the latest JTSDK on you should be linking in Hamlib-3 built > from my fork of the Hamlib development repo. > > There was an issue with the PkgConfig tool not being included in the JTSDK > which could case the wrong Hamlib version to be picked up. That issue has > recently been fixed by Greg. > > If you are getting ANY Hamlib libraries in the install 'bin' directory then > something is not correct in your build setup. > > The easiest way for me to check what you have is for you to send me the file > CMakeCache.txt from your build directory. >> Mike W9MDB > 73 > Bill > G4WJS. >> -----Original Message----- >> From: Bill Somerville [mailto:g4...@classdesign.com] >> Sent: Thursday, September 11, 2014 2:00 PM >> To: wsjt-devel@lists.sourceforge.net >> Subject: Re: [wsjt-devel] Back in town >> >> On 11/09/2014 19:40, John Nelson wrote: >>> Hi Bill and Joe, >> Hi John, >>> 1) What version of Qt are you compiling against? Qt5.2.1? I >> compiled a local version of Qt5.2.1 from source following your suggestion > to >> be able to get full c++11 support. But qt-project now has 5.3.1 >> available. Have you (or anyone) used this and should we incorporate > 5.3.1 >> in the beta version? Will it be necessary to compile from source again? >> I tried Qt 5.3.1 on Windows and everything compiled and linked OK. No >> changes required. I did hit a problem with building the install target >> on Windows with a Fortran secondary library not being pulled in by the >> fixup_bundle CMake script. For now I would suggest sticking with Qt >> 5.2.1 until I can get to the bottom of why that isn't working. >>> 2) Your new hamlib is "imminent". I'll wait for this before testing a >> Mac version on OSX 10.9.4. >> OK, I will keep the list updated with pushes to the public repo of my >> Hamlib-3 fork. >>> --- John G4KLA >>> >> 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 ------------------------------------------------------------------------------ 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
