hamlib-developer — hamlib developers forum

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 20 Jul 14:00 -0500, Diane Bruce via Hamlib-developer wrote:
> So we have backward compatibility for this. I'd go with the
> better_patch-tests_rigtestlibusb.c myself. 

Then that is what I'll do.  Thanks, Diane.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Diane B. <db...@db...>]

On Sun, Jul 20, 2025 at 12:18:06PM -0500, Nate Bargmann wrote:
> * On 2025 19 Jul 14:30 -0500, Diane Bruce via Hamlib-developer wrote:
> > There are some libusb changes for FreeBSD
> 
> > -    printf("      bU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
> > +    printf("      wU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
> > +#ifdef __FreeBSD__
> > +    printf("      wU2devExitLat:         %u\n", ss_usb_cap->wU2DevExitLat);
> > +#else
> 
> When I look at this, I'm confused.
> 
> Of the first two lines the 'b' is replaced by the 'w' in the in the
> printed string, but is left pointing to ss_usb_cap->bU1DevExitLat.
> Should the pointer or the string be changed, or neither, or both?

Mea culpa. I goofed. 
See first patch attached. Simple typo. I think I got the white space fixed
too.

A better patch (much simpler) is also attached.
see better_patch-tests_rigtestlibusb.c

Same comments apply but keep in mind 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 bNumDeviceCapsa

So we have backward compatibility for this. I'd go with the
better_patch-tests_rigtestlibusb.c myself. 


Anyway both versions compiled and tested and the second better version
works with current FreeBSD tree.


> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
> 

Sorry about the noise previously, I was hot and tired trying to get this into
the tree and working too fast.

Cheers!

- 73 Diane VA3DB
-- 
db...@Fr... db...@db... http://www.db.net/~db https://ottawa.place/@Dianora

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 14:30 -0500, Diane Bruce via Hamlib-developer wrote:
> There are some libusb changes for FreeBSD

> -    printf("      bU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
> +    printf("      wU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
> +#ifdef __FreeBSD__
> +    printf("      wU2devExitLat:         %u\n", ss_usb_cap->wU2DevExitLat);
> +#else

When I look at this, I'm confused.

Of the first two lines the 'b' is replaced by the 'w' in the in the
printed string, but is left pointing to ss_usb_cap->bU1DevExitLat.
Should the pointer or the string be changed, or neither, or both?

The third printf() inside the #if hints that the printf() prior to the
#if should point to ss_usb_cap->wU1DevExitLat and not
ss_usb_cap->bU1DevExitLat.

Is this correct?

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Diane B. <db...@db...>]

On Sat, Jul 19, 2025 at 09:59:13PM -0500, Nate Bargmann wrote:
> * On 2025 19 Jul 18:30 -0500, Diane Bruce via Hamlib-developer wrote:
> > On Sat, Jul 19, 2025 at 06:45:55PM -0400, Greg Troxel wrote:
> 
> > > I don't immediately understand; would be nice to include a commit
> > > message.
> > 
> > I should not have rushed but here we go. Sorry. :-(
> 
> Thanks Diane.  Good to see you on the list again.

Good to be back!

> 
> I think I can infer a commit message and I'll make sure the whitespace
> is not changed.

Yes sorry about that! Thanks! 73, Diane

> 
> 73, Nate
> 
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds.  The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
> 
> 
> 
> ----------
> 
> This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam:
> https://us2.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5f272629700ffd2504f91e28df364b66bc4b8cca5514aa436aa3a7ca0dbac997d927bcacef7892fb7c5829718786c5e58915b2c0ae6015651866158fe6f3cc41b66dce78b700a410e4e1eadd2d6383d65f2d2975dadb5b1960b80bfcd00ff650c6cd81d2ff98665e9a3b8ad22f571476dafb5533bbc1abe08eb6e8047e1e16dc0320a8326cd39f8897
> 
> 




> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer


-- 
db...@Fr... db...@db... http://www.db.net/~db https://ottawa.place/@Dianora

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 18:30 -0500, Diane Bruce via Hamlib-developer wrote:
> On Sat, Jul 19, 2025 at 06:45:55PM -0400, Greg Troxel wrote:

> > I don't immediately understand; would be nice to include a commit
> > message.
> 
> I should not have rushed but here we go. Sorry. :-(

Thanks Diane.  Good to see you on the list again.

I think I can infer a commit message and I'll make sure the whitespace
is not changed.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

[Hamlib-developer] [Hamlib/Hamlib] c14949: Rewrite

[Michael M. <no...@gi...>]

  Branch: refs/heads/master
  Home:   https://github.com/Hamlib/Hamlib
  Commit: c14949a86d34996764d0aa67e92bc8cfde361603
      https://github.com/Hamlib/Hamlib/commit/c14949a86d34996764d0aa67e92bc8cfde361603
  Author: Michael Morgan <844...@us...>
  Date:   2025-07-19 (Sat, 19 Jul 2025)

  Changed paths:
    M rigs/flexradio/smartsdr.c

  Log Message:
  -----------
  Rewrite

Rewrote it some to see if MinGW ok.



To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Diane B. <db...@db...>]

On Sat, Jul 19, 2025 at 06:45:55PM -0400, Greg Troxel wrote:
> Diane Bruce via Hamlib-developer
> <ham...@li...> writes:
> 
> > There are some libusb changes for FreeBSD
> 
> It's interesting that I don't seem to need these for NetBSD -- or might
> I not have noticed at build time?

You'd have noticed sorry I did not look at my NetBSD machine and code
tree. :) Obviously the code is different here.

See https://github.com/libusb/libusb/pull/1652
Perhaps maybe something like the suggested
#define wU2DevExitLat bU2DevExitLat

Also see https://reviews.freebsd.org/D50740

And this
#define bNumDeviceCapabilities bNumDeviceCaps
(see kevans comment)

Should make it work for all variations then. 

> 
> I wonder if this can be done with a configure test instead of ifdef
> FooOS, to be more likely to handle other situations.

It could easily be. I only did what I needed to make it run on FreeBSD
(Apart from my accidental whitespace change. oops!)
Perhaps using the defines would be cleaner?

> 
> There's a stray whitespace change.

Yes I only noticed I accidentally added this *sigh*.

> 
> I don't immediately understand; would be nice to include a commit
> message.

I should not have rushed but here we go. Sorry. :-(

> 
> 
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
> 
> ----------
> 
> This email has been scanned for spam and viruses by Proofpoint Essentials. Visit the following link to report this email as spam:
> https://us2.proofpointessentials.com/app/report_spam.php?mod_id=11&mod_option=logitem&report=1&type=easyspam&k=k1&payload=53616c7465645f5fa4a175933b97107c8bdca0f86642632becbb0eb65102f3e3dab8a57fae64c81bd2ef4c74d650ad23636bb424dd8e2b40e4f921d26ba2a1355d9aaa3349c12e790bcad46515e3848c8ba2add02c6db42904e1454641e61db62f5d9f650fb69df4201b01bd3ae7da4aa7c08f7aa6ce4cf3c9f2368d5da0b1bf828dfed54dff80f84875aa861eb7e3c6
> 

-- 
db...@Fr... db...@db... http://www.db.net/~db https://ottawa.place/@Dianora

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Greg T. <gd...@le...>]

Diane Bruce via Hamlib-developer
<ham...@li...> writes:

> There are some libusb changes for FreeBSD

It's interesting that I don't seem to need these for NetBSD -- or might
I not have noticed at build time?

I wonder if this can be done with a configure test instead of ifdef
FooOS, to be more likely to handle other situations.

There's a stray whitespace change.

I don't immediately understand; would be nice to include a commit
message.

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Diane B. <db...@db...>]

There are some libusb changes for FreeBSD


--- tests/rigtestlibusb.c.orig	2025-07-18 18:31:35 UTC
+++ tests/rigtestlibusb.c
@@ -116,8 +116,12 @@ static void print_ss_usb_cap(const struct
     printf("      bmAttributes:          %02xh\n", ss_usb_cap->bmAttributes);
     printf("      wSpeedSupported:       %u\n", ss_usb_cap->wSpeedSupported);
     printf("      bFunctionalitySupport: %u\n", ss_usb_cap->bFunctionalitySupport);
-    printf("      bU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
+    printf("      wU1devExitLat:         %u\n", ss_usb_cap->bU1DevExitLat);
+#ifdef __FreeBSD__
+    printf("      wU2devExitLat:         %u\n", ss_usb_cap->wU2DevExitLat);
+#else
     printf("      bU2devExitLat:         %u\n", ss_usb_cap->bU2DevExitLat);
+#endif
 }
 
 static void print_bos(libusb_device_handle *handle)
@@ -133,11 +137,17 @@ static void print_bos(libusb_device_handle *handle)
         return;
     }
 
+
     printf("  Binary Object Store (BOS):\n");
     printf("    wTotalLength:            %u\n", bos->wTotalLength);
+#ifdef __FreeBSD__
+    printf("    bNumDeviceCapabilities:          %u\n", bos->bNumDeviceCapabilities);
+    for (i = 0; i < bos->bNumDeviceCapabilities; i++)
+#else
     printf("    bNumDeviceCaps:          %u\n", bos->bNumDeviceCaps);
-
     for (i = 0; i < bos->bNumDeviceCaps; i++)
+#endif
+
     {
         struct libusb_bos_dev_capability_descriptor *dev_cap = bos->dev_capability[i];
 
@@ -172,7 +182,6 @@ static void print_bos(libusb_device_handle *handle)
             libusb_free_ss_usb_device_capability_descriptor(ss_dev_cap);
         }
     }
-
     libusb_free_bos_descriptor(bos);
 }
 

- 73 Diane VA3DB
-- 
db...@Fr... db...@db... http://www.db.net/~db https://ottawa.place/@Dianora

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 07:20 -0500, Dave Baxter via Hamlib-developer wrote:
> It was indeed the 4.7~git release that needed the ./bootstrap.
> 
> 
> The problem I have just now, is with grig I think.  (Whatever /dev/ttyUSB
> 'device' I specify, it always tries to open /dev/tty0 !)

The first order of business is to try with rigctl and see if the problem
still occurs.  If not, then it likely points to grig having an issue.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Dave B. <g8k...@go...>]

It was indeed the 4.7~git release that needed the ./bootstrap.


The problem I have just now, is with grig I think.  (Whatever 
/dev/ttyUSB 'device' I specify, it always tries to open /dev/tty0 !)

The repo version is very old, and the current source refuses to build.

Cheers All.

Dave G8KBV.



On 19/07/2025 13:06, Brian Morrison via Hamlib-developer wrote:
> On Sat, 19 Jul 2025 06:13:54 -0500
> Nate Bargmann<n0...@n0...> wrote:
>
>> * On 2025 19 Jul 05:38 -0500, Dave Baxter via Hamlib-developer wrote:
>>> Hi.
>>>
>>>
>>> I find that the with the release .tar files over the last few
>>> months, sometimes you need the ./bootstrap phase, sometimes you
>>> don't.  Sort of inconsistent...
>> Huh?
>>
>> That should most definitely NOT be required of the generated tarballs
>> EVER.  If it is, I consider that a serious bug and really need more
>> information.  In all my testing over the years I've not found this to
>> be the case, but I can't be everywhere on every system.
> I downloaded the tarball for 4.6.4 and then used rpmbuild with an
> updated .spec file on Fedora 42. It built and installed the rpm
> binaries perfectly, so thanks for the update Nate.
>
> Absolutely no need for ./bootstrap here.
>

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Brian M. <bd...@fe...>]

On Sat, 19 Jul 2025 06:13:54 -0500
Nate Bargmann <n0...@n0...> wrote:

> * On 2025 19 Jul 05:38 -0500, Dave Baxter via Hamlib-developer wrote:
> > Hi.
> > 
> > 
> > I find that the with the release .tar files over the last few
> > months, sometimes you need the ./bootstrap phase, sometimes you
> > don't.  Sort of inconsistent...  
> 
> Huh?
> 
> That should most definitely NOT be required of the generated tarballs
> EVER.  If it is, I consider that a serious bug and really need more
> information.  In all my testing over the years I've not found this to
> be the case, but I can't be everywhere on every system.

I downloaded the tarball for 4.6.4 and then used rpmbuild with an
updated .spec file on Fedora 42. It built and installed the rpm
binaries perfectly, so thanks for the update Nate.

Absolutely no need for ./bootstrap here.

-- 

Brian  G8SEZ

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 05:38 -0500, Dave Baxter via Hamlib-developer wrote:
> Hi.
> 
> 
> I find that the with the release .tar files over the last few months,
> sometimes you need the ./bootstrap phase, sometimes you don't.  Sort of
> inconsistent...

Huh?

That should most definitely NOT be required of the generated tarballs
EVER.  If it is, I consider that a serious bug and really need more
information.  In all my testing over the years I've not found this to be
the case, but I can't be everywhere on every system.

If you think this is required in the future, then please don't just
carry on, copy all of the output into a message and post it.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 03:43 -0500, gm3zza--- via Hamlib-developer wrote:
> My secret sauce is:
> 
> Open "Developer PowerShell for VS2022" in administrator mode. This
> adds the correct directory to the path and allows update of
> "C:\Program Files" with the .dll.
> 
> Then (in my case).
> 
> cd "C:\Program Files\hamlib-w64-4.6.4\lib\msvc"
> lib \def:libhamlib-4.def \machine:x64

I presume that "\machine:x64" would need to be changed to "\machine:x86"
for a 32 bit build?
 
> If you use any other terminal then the full path to lib.exe is needed
> (today it is  "C:\Program Files\Microsoft Visual
> Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\lib.exe",
> but is dependent on the version of MSVC which gets updated every few
> weeks).

Thank you!!!

>  The instructions in "C:\Program
>  Files\hamlib-w64-4.6.4\README.w64-bin.txt" needs to be trimmed a bit,
>  but we need to get more than just my current experience of having to
>  do this.

Please edit that file as you see fit and email it to me and I'll get it
incorporated into each script.  Alternatively, you can issue a PR
against the 'scripts/build-w32.sh' and 'scripts/build-w64.sh' files.
For each file the edits will likely start around line 187.

Thanks, Phil.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Dave B. <g8k...@go...>]

Hi.


I find that the with the release .tar files over the last few months, 
sometimes you need the ./bootstrap phase, sometimes you don't.  Sort of 
inconsistent...


Other than that...


./configure


followed by  (so long as that didn’t bomb) a 'make' and it all seems to 
build OK.


This is on a LMDE 6 (Debian 12 based) 64 bit, on an intel based machine.


At present, I now have "4.7~git from indeterminate source revision. 
64-bit", "Installed" unintentionally due to grey cell finger 
communication issues!  (Sources dated May 9th.)


And in an independent source tree location, 4.6.4.

(Sources dated July 18th or 19th.)


As well as the custom versions that came with WSJTx and JS8Call !   
(That I have so far failed to find out where they hide.)


All a bit of a muddle to manage I think.


73.


Dave G8KBV.




On 19/07/2025 10:17, gm3zza--- via Hamlib-developer wrote:
>
>
> Now to get 4.6.4 installed on debian, should be a lot easier.
>
> Silly me, of course it wasn't. I've forgotten how to use git to get a 
> specific branch so just gone ahead with the latest 4.7-git instead. 
> And this time my notebook failed me 🙁.
>
> Phil GM3ZZA
> ------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 19 Jul 04:18 -0500, gm3zza--- via Hamlib-developer wrote:
> 
> 
> Now to get 4.6.4 installed on debian, should be a lot easier.
> 
> Silly me, of course it wasn't. I've forgotten how to use git to get a
> specific branch so just gone ahead with the latest 4.7-git instead.
> And this time my notebook failed me 🙁.

Since 4.6.4 is now released, one should just download the release
tarball that has no need to use git.

To clone a specific branch, from the script I use to do just that:

git clone -b Hamlib-4.6.3 https://github.com/Hamlib/Hamlib.git hamlib

Note that I did not create a Hamlib-4.6.4 branch!  4.6.4 is a collection
of cherry-picked commits to fix bugs found after 4.6.3 and lives in the
Hamlib-4.6.3 branch.

I also do the same for the daily snapshots:

git clone -b master https://github.com/Hamlib/Hamlib hamlib

In this case it just speeds up the cloning process a bit since all the
refs for the different branches aren't retrieved.  For an ordinary clone
where all the repository history is wanted, I would not recommend this.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[<gm...@bt...>]

Now to get 4.6.4 installed on debian, should be a lot easier.

Silly me, of course it wasn't. I've forgotten how to use git to get a specific branch so just gone ahead with the latest 4.7-git instead. And this time my notebook failed me 🙁.

Phil GM3ZZA
________________________________

Re: [Hamlib-developer] Hamlib 4.6.4 release

[<gm...@bt...>]

My secret sauce is:

Open "Developer PowerShell for VS2022" in administrator mode. This adds the correct directory to the path and allows update of "C:\Program Files" with the .dll.

Then (in my case).

cd "C:\Program Files\hamlib-w64-4.6.4\lib\msvc"
lib \def:libhamlib-4.def \machine:x64

If you use any other terminal then the full path to lib.exe is needed (today it is  "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\Hostx64\x64\lib.exe", but is dependent on the version of MSVC which gets updated every few weeks).

 The instructions in "C:\Program Files\hamlib-w64-4.6.4\README.w64-bin.txt" needs to be trimmed a bit, but we need to get more than just my current experience of having to do this.

Now to get 4.6.4 installed on debian, should be a lot easier.

Phil GM3ZZA
________________________________
From: Nate Bargmann <n0...@n0...>
Sent: 19 July 2025 12:02 AM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Hamlib 4.6.4 release

* On 2025 18 Jul 16:48 -0500, gm3zza--- via Hamlib-developer wrote:
> Has anyone got the latest incarnation to create a .dll for MSVC x64? I
> now remember why I hardly ever update my Windows version of hamlib!

Some seem to have the recipe but apparently I don't have it either...

> I've got it somewhere in my notes, but....

"A cluttered desk is the sign of a cluttered mind."


"What's an empty desk a sign of?"

73, Nate

--
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

* On 2025 18 Jul 16:48 -0500, gm3zza--- via Hamlib-developer wrote:
> Has anyone got the latest incarnation to create a .dll for MSVC x64? I
> now remember why I hardly ever update my Windows version of hamlib!

Some seem to have the recipe but apparently I don't have it either...

> I've got it somewhere in my notes, but....

"A cluttered desk is the sign of a cluttered mind."


"What's an empty desk a sign of?"

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[<gm...@bt...>]

Has anyone got the latest incarnation to create a .dll for MSVC x64? I now remember why I hardly ever update my Windows version of hamlib!

I've got it somewhere in my notes, but....

73 Phil GM3ZZA
________________________________
From: Nate Bargmann <n0...@n0...>
Sent: 18 July 2025 8:15 PM
To: ham...@li... <ham...@li...>
Subject: Re: [Hamlib-developer] Hamlib 4.6.4 release

I forgot to include the download links.  D'oh!

https://sourceforge.net/projects/hamlib/files/hamlib/4.6.4/

https://github.com/Hamlib/Hamlib/releases/tag/4.6.4

73, Nate

--
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Philip R. <gm...@bt...>]

<div dir='auto'><div>I've found my notes. It's a job now for tomorrow. I've also got an action to test "Mike Black's update for the above"?</div><div dir="auto"><br></div><div dir="auto">Phil.<br><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">On 18 Jul 2025 22:27, gm...@bt... wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">
<div style="font-family:'aptos' , 'aptos_embeddedfont' , 'aptos_msfontservice' , 'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
Has anyone got the latest incarnation to create a .dll for MSVC x64? I now remember why I hardly ever update my Windows version of hamlib!</div>
<div style="font-family:'aptos' , 'aptos_embeddedfont' , 'aptos_msfontservice' , 'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style="font-family:'aptos' , 'aptos_embeddedfont' , 'aptos_msfontservice' , 'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
I've got it somewhere in my notes, but....</div>
<div style="font-family:'aptos' , 'aptos_embeddedfont' , 'aptos_msfontservice' , 'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
<br>
</div>
<div style="font-family:'aptos' , 'aptos_embeddedfont' , 'aptos_msfontservice' , 'calibri' , 'helvetica' , sans-serif;font-size:12pt;color:rgb( 0 , 0 , 0 )">
73 Phil GM3ZZA</div>
<div></div>
<hr style="display:inline-block;width:98%">
<div dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Nate Bargmann &lt;n0...@n0...&gt;<br>
<b>Sent:</b> 18 July 2025 8:15 PM<br>
<b>To:</b> ham...@li... &lt;ham...@li...&gt;<br>
<b>Subject:</b> Re: [Hamlib-developer] Hamlib 4.6.4 release</font>
<div>&nbsp;</div>
</div>
<div><font size="2"><span style="font-size:11pt">
<div>I forgot to include the download links.&nbsp; D'oh!<br>
<br>
<a href="https://sourceforge.net/projects/hamlib/files/hamlib/4.6.4/">https://sourceforge.net/projects/hamlib/files/hamlib/4.6.4/</a><br>
<br>
<a href="https://github.com/Hamlib/Hamlib/releases/tag/4.6.4">https://github.com/Hamlib/Hamlib/releases/tag/4.6.4</a><br>
<br>
73, Nate<br>
<br>
-- <br>
"The optimist proclaims that we live in the best of all<br>
possible worlds.&nbsp; The pessimist fears this is true."<br>
Web: <a href="https://www.n0nb.us">https://www.n0nb.us</a><br>
Projects: <a href="https://github.com/N0NB">https://github.com/N0NB</a><br>
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819<br>
<br>
</div>
</span></font></div>
</div>
</blockquote></div><br></div></div></div>

Re: [Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

I forgot to include the download links.  D'oh!

https://sourceforge.net/projects/hamlib/files/hamlib/4.6.4/

https://github.com/Hamlib/Hamlib/releases/tag/4.6.4

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

[Hamlib-developer] Hamlib 4.6.4 release

[Nate B. <n0...@n0...>]

Hi All.

Realizing that today is Hamlib's 25th birthday, I thought it would be
nice to just release 4.6.4 as a present to everyone!

This is a bug fix release with no new device support.

Changes are:

Version 4.6.4
        * 2025-07-18--Hamlib's 25th birthday!!!
        * Fix handling of unprintable characters in kenwood.c that broke radios
          such as the TM-D710/TM-V71 that use EOM_TH (\r) as the command terminator.
          (TNX, Lars Kellogg-Stedman and George Baltz).
        * Fixed jrc_set_chan. (TNX Mark Fine).
        * Fix memory leak in rigctl_parse.c and use unique separator character
          for each rigctld connection--closes GitHub #1748. (TNX George Baltz).
        * Fix powerstat check for Icom R75 which rejects the command.  (TNX Mark Fine).
        * Restore TS-590S/SG RIG_LEVEL_RFPOWER_METER, Fix rotctl \dump_caps output
          (TNX, George Baltz).
        * Add CW sending capability to Flex SmartSDR.  (TNX Michael Morgan)
        * Handle spaces correctly for Fles SmartSDR.  (TNX Michael Morgan)

There may be a few more bugs that can be squashed in this branch leading
to 4.6.5, but right now that seems some time off.  Otherwise development
is moving toward the 4.7.0 release later this year.

73, Nate

-- 
"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."
Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

[Hamlib-developer] [Hamlib/Hamlib]

[Nate B. <no...@gi...>]

  Branch: refs/tags/4.6.4
  Home:   https://github.com/Hamlib/Hamlib

To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications

[Hamlib-developer] [Hamlib/Hamlib] 59e3d1: Advance to Hamlib 4.6.4

[Nate B. <no...@gi...>]

  Branch: refs/heads/Hamlib-4.6.3
  Home:   https://github.com/Hamlib/Hamlib
  Commit: 59e3d1b307504440837c3a5c24a15d7038e59f69
      https://github.com/Hamlib/Hamlib/commit/59e3d1b307504440837c3a5c24a15d7038e59f69
  Author: Nate Bargmann <n0...@n0...>
  Date:   2025-07-18 (Fri, 18 Jul 2025)

  Changed paths:
    M NEWS
    M configure.ac

  Log Message:
  -----------
  Advance to Hamlib 4.6.4



To unsubscribe from these emails, change your notification settings at https://github.com/Hamlib/Hamlib/settings/notifications