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