Get rid of messages about missing C++ initializers
a) The structure is always built in C code
b) calloc() is a very good initializer
And make a few routines static
In struct SensorData, GLFloat was used to store 3 floats. However, the
code doesn't perform any GLSL calculation on them. More, Termux doesn't
provide GLSL headers and fails to build. This commit refactos GLFloat
to float to avoid necessary header issues, etc.
Signed-off-by: Gong BI1XJT <bi1xjt@rad1o.cn>
To use the Skywatcher rotator, both motors have to by initialized. When
using the direct mode of the mounts hand control unit, this
initialization is performed by the hand control. We just need to set the
position.
When using the motor driver directly with a simple USB-RS232-adapter,
this init command must be sent before we are able to steer the mount.
This allows us to use the mount without cabeling up the whole hand
control unit.
Turn off -x option in cppcheck.sh, fix missing '\'.
This fixes all the "error" messages from cppcheck except those
due to its own inability to handle concatenated format strings.
This allows to connect to the server running on another machine
or on a different port.
Defaults to the old value of localhost:7624.
It is still possible to connect to the local domain, eg. with
--rot-file @/tmp/indiserver
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
According to iwyu, to avoid unecessary rebuilds and to reduce the
chances of breakages of the build if includes are rearranged, the
code that uses serial_open() and ser_close() should include
serial.h while the code that uses read_block() write_block() and
similar should include iofunc.h, code that uses all of them should
include both files.
Found with iwyu.
Many (most?) of the uses of the port structures in Hamlib are to pass through
to the basic I/O routines (rig_flush(), write_block(), read_string()),
without referencing any of the structure data. Don't bother including
port.h if it won't be used.
The ???PORT macros are independent of actual hamlib_port_t data use.
