Options availables are:
./configure # same as --with-cxx-binding=detect
./configure --with-cxx-binding=detect # build if prerequisites are met
./configure --with-cxx-binding=no # do not build
./configure --without-cxx-binding # do not build
./configure --with-cxx-binding=yes # fail if prerequisites aren't met
Options availables are:
./configure # same as --with-indi=detect
./configure --with-indi=detect # build if prerequisites are met
./configure --with-indi=no # do not build
./configure --without-indi # do not build
./configure --with-indi=yes # fail if prerequisites aren't met
It has several issues:
* these are trace messages so RIG_DEBUG_ERR is inappropriate
* they are in a custom format which doesn't handle end of line chars
* write_block() and read_string() print the same information when
debug level is set to TRACE
Needed to adjust one of the timeouts. Was causing issues on Windows. Also made some changes due to IF command response size being 30, it was erroring out. And last band mapping was a little different on this rig for 2m, 70cm, 4m and Air Band.
If the earlier macro AC_PROG_CXX found a compiler that needs some
arguments, the variable CXX will contain also the arguments, so the
macro AC_CHECK_PROG will try to find a file that doesn't exist
(such as "g++ -std=gnu++11" instead of just "g++").
If AC_PROG_CXX didn't find a compiler, the variable CXX is empty.
At some time, the commented out line check_PROGRAMS removed by this commit was
identical to the line following it, plus testsecurity appended, then they went
out of sync.
The commented out line check_PROGRAMS added by this commit appends testsecurity
in an explicit way.
The needed value is already in the variable.
Test case /to check that the changes don't break the code):
tests/rigctl --set-conf=rig_pathname=test,write_delay=1,timeout=2 --show-conf Q | grep --no-group-separator -A1 -E "(rig_pathname|^write_delay|^timeout):"
tests/rotctl --set-conf=rot_pathname=test,write_delay=1,timeout=2 --show-conf Q | grep --no-group-separator -A1 -E "(rot_pathname|^write_delay|^timeout):"
The output before and after this patch is:
rig_pathname: "Path name to the device file of the rig"
Default: /dev/rig, Value: test
write_delay: "Delay in ms between each byte sent out"
Default: 0, Value: 1
timeout: "Timeout in ms"
Default: 0, Value: 2
Command 'Q' not found!
rot_pathname: "Path name to the device file of the rotator"
Default: /dev/rotator, Value: test
write_delay: "Delay in ms between each byte sent out"
Default: 0, Value: 1
timeout: "Timeout in ms"
Default: 0, Value: 2
This fixes the following commands that always printed debug messages
at the trace level:
tests/ampctld -l >/dev/null
tests/ampctl -h >/dev/null
tests/rigctld -l >/dev/null
tests/rigctltcp -l >/dev/null
tests/rotctld -l >/dev/null
It doesn't affect other software which worked around this issue,
but changes all software to avoid regressions in future.
Test case (should print nothing in bash):
{
tests/ampctl -l -h
tests/ampctld -l -h
tests/rigctl -l -h
tests/rigctlcom -l -h
tests/rigctld -l -h
tests/rigctlsync -l -h
tests/rigctltcp -l -h
tests/rotctl -l -h
tests/rotctld -l -h
} >/dev/null
Nate Bargmann