Since Python 3.12, strings such as:
f"test_{object_name.replace(".", "_")}_class.py"
are allowed but older versions require single quotes around the dot and
underscore within the double quoted string.
Should quell CI error on Ubuntu Noble.
FreeBSD will eventually have the less verbose bNumDeviceCaps instead of
bNumDeviceCapabilities The other changes are (hopefully) to be
upstreamed renaming bU2devExitLat to wU2devExitLat
FreeBSD in the head of the tree has
/usr/include/libusb20_desc.h:#define bNumDeviceCapabilities bNumDeviceCaps
So we have backward compatibility for this.
Fails on bot Linux and Mac for different reasons.
On Linux:
ERROR: files left after uninstall:
./lib/x86_64-linux-gnu/perl/5.40.1/Hamlib.pm
./lib/x86_64-linux-gnu/perl/5.40.1/auto/Hamlib/Hamlib.so
./lib/x86_64-linux-gnu/perl/5.40.1/auto/Hamlib/.packlist
./lib/x86_64-linux-gnu/perl/5.40.1/perllocal.pod
make[1]: *** [Makefile:921: distuninstallcheck] Error 1
On Mac:
Can't load 'blib/arch/auto/Hamlib/Hamlib.bundle' for module Hamlib: dlopen(blib/arch/auto/Hamlib/Hamlib.bundle, 0x0001): Library not loaded: /Users/runner/work/Hamlib/Hamlib/hamlib-4.7~git/_inst/lib/libhamlib.4.dylib
Referenced from: <0FE3328D-6834-37EA-9827-03864B87CEA4> /Users/runner/work/Hamlib/Hamlib/hamlib-4.7~git/_build/sub/bindings/blib/arch/auto/Hamlib/Hamlib.bundle
Reason: tried: '/Users/runner/work/Hamlib/Hamlib/hamlib-4.7~git/_inst/lib/libhamlib.4.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/Users/runner/work/Hamlib/Hamlib/hamlib-4.7~git/_inst/lib/libhamlib.4.dylib' (no such file), '/Users/runner/work/Hamlib/Hamlib/hamlib-4.7~git/_inst/lib/libhamlib.4.dylib' (no such file) at /opt/homebrew/opt/perl/lib/perl5/5.40/darwin-thread-multi-2level/DynaLoader.pm line 210.
at blib/lib/Hamlib.pm line 11.
- Add FTX-1 rig model (ID 840) to riglist.h
- Create ftx1.c and ftx1.h with FTX-1 implementation
- Add FTX-1 to Yaesu Makefile.am
- Integrate FTX-1 into newcat.c command validation system
- Update yaesu.c and yaesu.h for FTX-1 support
- Based on FT-991A CAT protocol compatibility
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.
Compiling with NO_OLD_INCLUDES still won't work until the state
structure(s) are moved out of rig_struct, but at least I get the
right compiler errors.
Michael Morgan