Hi Steve
It actually broke my fldigi/hamlib alpha builds. ie 4.2.06.18 and
19 now fails with Hamlib 4.7~git 2024-12-29T16:43:39Z SHA=028d75
64-bit (and later)
rigcontrol/hamlib.cxx: In function ¡®void hamlib_get_rigs()¡¯:
rigcontrol/hamlib.cxx:612:26: error: invalid conversion from ¡®int
(*)(rig_caps*, void*)¡¯ to ¡®int (*)(const rig_caps*, void*)¡¯
[-fpermissive]
? 612 |???????? rig_list_foreach(add_to_list, 0);
????? |????????????????????????? ^~~~~~~~~~~
????? |????????????????????????? |
????? |????????????????????????? int (*)(rig_caps*, void*)
In file included from ./include/rigclass.h:27,
???????????????? from ./include/main.h:36,
???????????????? from ./include/squelch_status.h:31,
???????????????? from ./include/status.h:29,
???????????????? from ./include/nanoIO.h:42,
???????????????? from ./include/confdialog.h:424,
???????????????? from rigcontrol/hamlib.cxx:34:
/usr/local/include/hamlib/rig.h:3794:18: note:?? initializing
argument 1 of ¡®int rig_list_foreach(int (*)(const rig_caps*,
void*), void*)¡¯
?3794 | rig_list_foreach HAMLIB_PARAMS((int (*cfunc)(const struct
rig_caps *, rig_ptr_t),
Cheers Bob VK2YQA
On 3/1/25 08:24, Steve, KB5AW via
groups.io wrote:
toggle quoted message
Show quoted text
Hamlib has recently reverted the change that broke fldigi
hamlib control build with this comment:
Change rig_list_foreach back to using
const argument -- was breaking many C++ application builds
?
I expect that this will fix fldigi hamlib control.
_._,_._,_
