Hi Bill, See below,
On 9/11/2014 21:24, Bill Somerville wrote: > On 11/09/2014 21:43, KI7MT wrote: >> Hi Bill, Mike, > Hi Greg, >> >> Just FYI >> >> I just built both Debug and Release install targets, and the only thing >> Hamlib related in the Build Tree are the .cpp.obj and .cpp files, which >> should be there I would expect. >> >> The install directories are clear of any Hamlib files. I verified the >> Debug wsjtx.bat in the Debug\install directory, it is pointing to: >> >> c:\JTSDK-QT\hamlib3\bin >> >> Which it should be. > It's not required although it is probably best left in since at some > point in the future Hamlib-3 will be publicly released and we can then > revert to dynamically linking to their shared library and picking it up > via PATH when executing Debug configured build artefacts. Yes, from our past conversation, just thought it best to have it standard for when things are released it uses the same method to pull from hamlib3 for dynamic in Debug. >> >> However!!, I did find an error in the Debug batch file creation. It's >> calling "wsjtx.exe" rather than the "wsjtx.bat" file which sets the >> paths to Hamlib3 and FFTW and the other QT runtime libs. > OK, again Hamlib-3 is not needed but is benign and best left in. >> >> This would only be an issue is running from the Debug Install directory: >> >> C:\JTSDK-QT\wsjtx\install\Debug\bin >> >> But, I would expect the user would get runtime gcc lib missing errors >> before they made it to the UI. > Indeed. >> >> I'll send a fix shortly to correct the batch file generation. >> >> 73's >> Greg, KI7MT > 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 > -- 73's Greg, KI7MT ------------------------------------------------------------------------------ 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
