I manually fixed the cache file to point to hamlib3 rigctld.exe

I'm using "build wsjtx rinstall"

Now I see
Install the project...
-- Install configuration: "Release"
-- Up-to-date: C:/JTSDK-QT/wsjtx/install/Release/bin/wsjtx.exe
-- Up-to-date: C:/JTSDK-QT/wsjtx/install/Release/bin/jt9.exe
-- Up-to-date: C:/JTSDK-QT/wsjtx/install/Release/bin/jt65code.exe
-- Up-to-date: C:/JTSDK-QT/wsjtx/install/Release/bin/jt9code.exe
-- Up-to-date: C:/JTSDK-QT/wsjtx/install/Release/bin/kvasd.exe
-- Installing: C:/JTSDK-QT/wsjtx/install/Release/bin/rigctld.exe
-- Installing: C:/JTSDK-QT/wsjtx/install/Release/lib/plugins/platforms
-- Installing:
C:/JTSDK-QT/wsjtx/install/Release/lib/plugins/platforms/qwindows.
-- fixup_exe: C:/JTSDK-QT/wsjtx/install/Release/bin/wsjtx.exe
-- fixup_bundle
--   app='C:/JTSDK-QT/wsjtx/install/Release/bin/wsjtx.exe'
--
libs='C:/JTSDK-QT/wsjtx/install/Release/lib/plugins/platforms/qwindows.dll'
--   dirs='/JTSDK-QT/fftw3f'
-- fixup_bundle: preparing...
--
warning: cannot resolve item 'libhamlib-2.dll'

And this is what I end up with in wsjxt\install\Release\bin  (with libham
missing of course)
Directory of C:\JTSDK-QT\wsjtx\install\Release\bin

09/11/2014  03:37 PM    <DIR>          .
09/11/2014  03:37 PM    <DIR>          ..
09/11/2014  03:37 PM        22,378,434 icudt51.dll
09/11/2014  03:37 PM         3,369,922 icuin51.dll
09/11/2014  03:37 PM         1,978,690 icuuc51.dll
09/11/2014  03:27 PM           680,298 jt65code.exe
09/11/2014  03:27 PM           861,842 jt9.exe
09/11/2014  03:27 PM           678,068 jt9code.exe
09/11/2014  03:27 PM           185,344 kvasd.exe
09/11/2014  03:37 PM         2,446,144 libfftw3f-3.dll
09/11/2014  03:37 PM           544,817 libgcc_s_dw2-1.dll
09/11/2014  03:37 PM         1,098,392 libgfortran-3.dll
09/11/2014  03:37 PM           487,816 libquadmath-0.dll
09/11/2014  03:37 PM           989,805 libstdc++-6.dll
09/11/2014  03:37 PM            73,901 libwinpthread-1.dll
09/11/2014  03:34 PM                35 qt.conf
09/11/2014  03:37 PM         4,607,488 Qt5Core.dll
09/11/2014  03:37 PM         4,624,896 Qt5Gui.dll
09/11/2014  03:37 PM           824,320 Qt5Multimedia.dll
09/11/2014  03:37 PM         1,393,152 Qt5Network.dll
09/11/2014  03:37 PM         6,282,752 Qt5Widgets.dll
03/27/2014  11:36 AM           322,872 rigctld.exe
09/11/2014  03:28 PM         5,871,848 wsjtx.exe


-----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

Reply via email to