[Ham-Mac] flrig alpha test version 1.3.40.34 posted
w1hkj
w1hkj at bellsouth.net
Fri Apr 20 18:34:06 EDT 2018
This alpha release is the culmination of several man months of
development and testing. Please study the howto.txt file which you can
download from the w1hkj.com web site and is included below. If you
experience issues with the software you need to be lucid in your bug
reports. Check the commit-history.txt file (also below) to see if your
transceiver had support code changes introduced by version 1.3.40.34.
Download from http://www.w1hkj.com/alpha/flrig/
or click on these links for the file(s) needed for you operating system:
* commit-history.txt <http://www.w1hkj.com/alpha/flrig/commit-history.txt>
* flrig-1.3.40.34.tar.gz
<http://www.w1hkj.com/alpha/flrig/flrig-1.3.40.34.tar.gz>
* flrig-1.3.40.34_i386.dmg
<http://www.w1hkj.com/alpha/flrig/flrig-1.3.40.34_i386.dmg>
* flrig-1.3.40.34_macos.dmg
<http://www.w1hkj.com/alpha/flrig/flrig-1.3.40.34_macos.dmg>
* flrig-1.3.40.34_ppc.dmg
<http://www.w1hkj.com/alpha/flrig/flrig-1.3.40.34_ppc.dmg>
* flrig-1.3.40.34_setup.exe
<http://www.w1hkj.com/alpha/flrig/flrig-1.3.40.34_setup.exe>
* howto.txt <http://www.w1hkj.com/alpha/flrig/howto.txt>
------------------------------------------------------------------------
*howto.txt*:
You may need to change the type and depth of the test report files.
========================================================================
On Linux/Unix:
$ cd flrig-1.3.40.34
$ ./configure && make
$ src/flrig --RIG_DEBUG
if you want to test with a clean slate for the configuration files:
$ src/flrig --config-dir TESTDIR --RIG_DEBUG
The test report files: debug_log.txt, and trace.txt will be located in
either $HOME/.flrig, or ./TESTDIR depending on whether you used the
--config-dir parameter.
Running from within a gnu debugger session:
$ gdb src/flrig
(gdb) handle SIGUSR2 -nostop
(gdb) run --RIG_DEBUG
or
(gdb) run --RIG_DEBUG --config-dir TESTDIR
The program will return to the gdb prompt if the program faults. If and
when it does you examine the fault execution path using the backtrace
command:
(gdb) bt
(gdb) q
========================================================================
On OS-X
After installing from the dmg the unix binary "flrig" will be located in
the folder
/Applications/flrig-1.3.40.34.app/Contents/MacOS/
Open a terminal window:
$ cd
$ mkdir flrig-test
$ cd flrig-test
$ cp /Applications/flrig-1.3.40.34.app/Contents/MacOS/flrig .
$ ./flrig --RIG_DEBUG
or
$ ./flrig --config-dir TESTDIR --RIG_DEBUG
The test report files: debug_log.txt, and trace.txt will be located in
either $HOME/.flrig, or ./TESTDIR depending on whether you used the
--config-dir parameter.
Running from within an OS-X debugger session:
$ lldb src/flrig
(lldb) process handle SIGUSR2 -n false -p true -s true
(lldb) run --RIG_DEBUG
or
(lldb) run --RIG_DEBUG --config-dir TESTDIR
The program will return to the lldb prompt if the program faults. If and
when it does you examine the fault execution path using the backtrace
command:
(lldb) bt
(lldb) q
========================================================================
On Windows:
(1)
Open the desktop launch icon for flrig-1.3.40.34 properties dialog
Modify the target control contents by adding " --RIG_DEBUG"
the test result files, debug_log.txt and trace.txt will be located in
the default flrig files folder, "flrig.files"
or
(2) (if you are comfortable with command line processing on Windows)
a. Open the file explorer and create a new folder in your home folder
"flrig-test"
b. Locate the flrig binary for flrig-1.3.40.34 in you "progam" folder(s).
This location is dependent upon the verion of Windows.
c. Copy the "flrig.exe" file to your new "flrig-test" folder
d. Open a command terminal and change folder to the "flrig-test" folder
e. proceed similarly to Linux/Unix/OS-X at the command prompt
./flrig.exe --RIG_DEBUG (test files in the default "flrig.files"
folder.
or
./flrig.exe --RIG_DEBUG --config-dir TESTDIR (test files in the
TESTDIR folder within "flrig-test" folder.
Sorry, but I have no easy way to recommend using any of the MS debugging
tools.
========================================================================
On all of the OS, when executing from a command line you can view the
command line parameter options:
$ ./flrig --help
------------------------------------------------------------------------
*commit-history.txt*:
Commit History post Version 1.3.39
Commit Name
5d40424 alpha
c9bbd40 Conditional trace
38c3255 Warnings fixes
b067eba FT950 debug
4bf2ac6 Icom updates
8e7228f FT891 debug
2946e47 Vfo-B mode
8526ef2 Load prefs file
2d42c2f Exit processing
a4f2190 appbundle
6360f33 Init no split
a00a7a6 xmlrpc method swap
24c4895 altvfo
ded9ad8 FT series vfo
f4d5f2e Service queues
65fb95f replystr mutex
6f770c0 ptt race / debug trace
f41e8a1 xmlrpc a/b vfo
a23d9fa ICbase
8f4a204 Split operation
7c88d0f TT588
bb31cf0 xmlrpc help
60dcf2e xmlrpc swap/split
f6e55f7 Yaesu ID
47a8dc0 Mode change
Modified/Added files:
scripts/
mkappbundle.sh
src/UI/
rigpanel.cxx
ui_small.cxx
ui_touch.cxx
ui_wide.cxx
xcvr_setup.cxx
src/include/
FT2000.h
IC7100.h
IC7300.h
IC7410.h
IC7600.h
IC7800.h
IC7851.h
IC9100.h
dialogs.h
rig.h
rig_io.h
rigbase.h
status.h
support.h
xml_server.h
src/
main.cxx
src/rigs/
FT2000.cxx
FT450.cxx
FT450D.cxx
FT5000.cxx
FT847.cxx
FT857D.cxx
FT891.cxx
FT950.cxx
FT991.cxx
FT991A.cxx
FTdx1200.cxx
FTdx3000.cxx
FTdx9000.cxx
IC7000.cxx
IC703.cxx
IC706MKIIG.cxx
IC7100.cxx
IC718.cxx
IC7200.cxx
IC7300.cxx
IC735.cxx
IC7410.cxx
IC746.cxx
IC756.cxx
IC756PRO2.cxx
IC756PRO3.cxx
IC7600.cxx
IC7800.cxx
IC7851.cxx
IC9100.cxx
ICbase.cxx
PCR1000.cxx
TS2000.cxx
TS590S.cxx
TS590SG.cxx
TS870S.cxx
TT588.cxx
rigbase.cxx
src/server/
xml_server.cxx
src/support/
debug.cxx
dialogs.cxx
ptt.cxx
rig_io.cxx
status.cxx
support.cxx
tod_clock.cxx
------------------------------------------------------------------------
Thanks. This commit has been pushed to Source Forge repository, flrig pu/df.
73, David, W1HKJ
More information about the Ham-Mac
mailing list