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