This is necessary to keep alignment between the client view of rig->state and the shared libarary view
Including PTHREAD functions in rig->state necessitated this as HAVE_PTHREAD only defined during hamlib compilation.
Clients including hamlib/rig.h did not pick up all the HAVE* config variable that control what gets included
https://github.com/Hamlib/Hamlib/issues/947
Change hamlib_port_t to a pointer in rig.state
Deprecate static hamlib_port_t structure
New hamlib_port_t structure at end of rig.state
Clients built with older hamlib will use old structure in DLL
Clients built with newer hamlib will use new structure in DLL
So we maintain backwards compatibility until Hamlib 5.0
https://github.com/Hamlib/Hamlib/issues/894
file.
There is no point in having it in the header file if data that is used only in
the C file.
Export ft857_[sg]et_vfo via the ft857 header and use the header in
ft897.
rig_s was assigned once and use once, better use rig->state direct;
it gives less code to read.
Also dramatically shrinked send_priv_cmd for ft1000mp, ft100, ft600,
ft747 and ft847 by simply using ncmd direct instead of via a variabel.
Fixed using the following command:
codespell --write-changes --summary --skip=*.m4 --ignore-words-list="develope,get's,quitt,setts,som,ue,vektor"
codespell --write-changes --summary --skip=aclocal.m4,lib --ignore-words-list="develope,get's,quitt,setts,som,ue,vektor"
Codespell home page: https://github.com/codespell-project/codespell
Add README.freqranges to explain what's going on with this feature
Add default ITU definitions to bandplan.h
The ITU definitions will likely change as the backends are updated dependinggg on the rig models
https://github.com/Hamlib/Hamlib/issues/243
Power levels and ranges need to be verified
Plus is there more than one FT847 model...e.g. a U.K. version?
I see FT847 mods to open up 4M so this may just be a customization.
https://github.com/Hamlib/Hamlib/issues/243