Skip to content

Hamlib5 compatibility#4

Open
GeoBaltz wants to merge 4 commits into
WSJTX:masterfrom
GeoBaltz:hamlib5
Open

Hamlib5 compatibility#4
GeoBaltz wants to merge 4 commits into
WSJTX:masterfrom
GeoBaltz:hamlib5

Conversation

@GeoBaltz

Copy link
Copy Markdown

Patches to adapt WSJT-X to Hamlib 5.0 changes

Use rig_set_conf() for port setup - remove referencing Hamlib internal structures.
Use new methods/macros to access Hamlib state structures when API functions not adequate.

First two commits allow compilation&execution with either Hamlib 4.7.x or 5.0~git. Third commit is a non-working attempt to broaden that to include 4.6.x and 4.5.x - so far unsuccessful.

Would this be acceptable (if completed)? What does this need, as far as style or formatting?

Comments, PLEASE

73 n3gb

GeoBaltz added 4 commits April 9, 2026 14:35
Don't touch hamlib internal structure - use rig_set_conf() instead.
Compiles on either Hamlib 4.7.x or 5.0.
Updates state and port access methods for new Hamlib structures, using
  macros for backward compatibility.

Needs CMakeLists.txt changes to only include new definitions if they
  exist(4.7.0 or later)
Attempt to get cmake to define variable for existence of include files.
Always says it's "" - no include found.

Is it because the files are in /usr/local/include?
Or is this just wrong?
Just check for the existence of .h files
Add one more set of parens
@GeoBaltz

Copy link
Copy Markdown
Author

New commit added - fixes use with Hamlib 4.5, 4.6. May even work with 4.4.

Builds and runs with Hamlib-5.0.0~git

@GeoBaltz GeoBaltz marked this pull request as ready for review April 30, 2026 19:50
@KJ5HST

KJ5HST commented May 10, 2026

Copy link
Copy Markdown
Contributor

Thanks, George. I'll try to take a look at it this week unless one of the others beats me to it. I might not get to it until after Dayton. I'd also like to collaborate more on Hamlib 5 moving forward. There are some integration matters that we should discuss sooner rather than later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants