OK Bill - I'm lost! Here is what I've done so far.
First, I thought it would be easier to simply edit the CMakeCache.txt file. I
looked at the existing contents of the file and noticed that the majority of
the lines in there had the :BOOL= parameter on them. So, using nano, I found a
likely spot down low in the file and added your five lines, plus a "comment"
line above them, like thus:
//Trace options set per Bill Somerville.WSJT_TRACE_CAT:BOOL=ON...... etc.
I then saved the file, and ran: sudo cmake --build . --target install -- -j2
That appeared to run OK. I started up WSJT-X but no *trace.log was found,
either during operation or afterwards, so I suspect I've done something
incorrect. Not surprising, as I'm only guessing what a lot of these commands
are doing. Any ideas?
Also - got no idea how to get the cmake-gui to fire up.
Jim / W6JHB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Wednesday, April 13, 2016 11:49 AM
Subject: Re: [wsjt-devel] 6616 Frequency "Shift" Issue
On 13/04/2016 19:35, Jim Bennett wrote:
> Yes, the rigctl-wsjtx command is MUCH easier than the other! :-) I did
> it and pasted towards the bottom of this message is the result. I have
> made a discovery no this one as I've been writing this message. If I
> give it an even number for the frequency (i.e. 14076000), it looses
> that one Hertz and returns 14075999. If I give it an odd number
> (14077000) it returns the requested frequency. Dang computers!
>
> Another thing I'm finding is a problem with transmit on JT9 or JT65.
> If I click on the Tune button, or call CQ, or answer another CQ, my
> transmission ends after anywhere from 8 - 20 seconds. If I then try
> another transmission, I get the following error message on the
> terminal output panel:
>
> 16-04-13T16:00:35.268Z: Hamlib: si570xxxusb_get_freq_by_value:
> libusb_control_transfer failed: LIBUSB_ERROR_PIPE
>
Hi Jim,
I was expecting more trace output from rigctl-wsjtx, can you try again
with another v like:
rigctl-wsjtx -m 2517 -vvvvvv F 14076000 f
The interrupted transmission will probably need the trace from WSJT-X.
Doing the instrumented build is not so hard, just run cmake-gui with one
argument which is the directory that is the build directory. Tick the
"Grouped" check box and then find the options I listed and check them.
The WSJT_HAMLIB_VERBOSE_TRACE one will not show until you have set
WSJT_HAMLIB_TRACE=ON and clicked "Configure". When they are all set
click "Configure" then "Generate" and quit then rebuild:
cmake --build <build-root> --target install -- -j2
or similar. The build will take a while as changing those options will
cause everything to recompile.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
