Replies: 2 comments
-
Ok so it must be something whacked with my primary pc. I built out a virtual box and was just trying to clean up my notes on what I did to get it to work, although they have one gap somewhere I was able to build it and didn't have the problems with HamLib or it crashing so far. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Just for anyone in the future I found the cause. I had an entry for JTDX in my system path, so it was using a different version of Hamlib and causing the crash. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
LadisLiv (or anyone else) I have started using a Hermes Lite 2 as my main radio and for that I am using the Thetis software which works great with QLog. But I am trying to get to where I can build and play with QLog. I have gotten to the point where I can compile it works ok with one exception. It will crash if I try to connect to either my radio or rotor which uses HamLib. So I am guessing there is something up with the way I am binding to that DLL and I was hoping to get a little help. I will go through and try to document what I have done to this point to get it to work (if I can step through it). But for HamLib this is what I did:
I installed the Hamlib 4.5.5 installer (hamlib-w64-4.5.5.exe) then in looking at the documentation I ran the following command in (C:\Program Files\hamlib-w64-4.5.5\lib\msvc) ["C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.41.34120\bin\Hostx64\x64\link.exe" /lib /machine:X64 /def:libhamlib-4.def]
When I did that QT complains saying it cannot find hamlib.lib so I made a copy of libhamlib-4.lib to be hamlib.lib. When I did that it will build and run without issue. Until I try to connect to a radio/rotor using hamlib. It will also crash if I try to open settings which I think is related to opening hamlib to query the rig and rotor list.
I have run a debug and the last line is always something with HamLib. For instance, if I try and connect to a rig, I see this:
rig_has_get_parm called
Or rotor:
rot_get_ext_parm called
rot_get_ext_func called
Or when I open the settings form:
rig_has_get_parm called
rot_get_ext_parm called
rot_get_ext_level called
I feel like I am doing some simple and wrong with Hamlib but not sure what it is.
Thanks for any help.
Michael, AA5SH
Beta Was this translation helpful? Give feedback.
All reactions