All External Packages were updated to provide VS2022 support (via a minor update to vstool.cmd), and as a result, have been rebuilt so that Hercules's reported "HHC01417I Built with..." messages for each now accurately report their actual current repository version.
This is actually just a "cosmetic" update since none of the actual logic of any of the External Packages has actually changed. Only the version strings have changed. Not the actual logic.
This should be a cosmetic change for those who build the External Packages themselves.
For those who don't however (i.e. for those who build and link Hercules with the default ExtPkg lib files that come pre-delivered with the Hercules distribution, this should update all ExtPkgs to their latest and greatest version.
Due to a recently discovered CMake build script bug in the External Packages, the actual cpu architecture of the resulting static libs were all the same (i.e. the so-called 32-bit libs, named libcrypto32.a, libdecNumber32.a, libSoftFloat32.a and libtelnet32.a, were actually 64-bit, not 32-bit).
This commit is to simply update all of the extpkg libs with the latest version, which, having now all been built with the fixed CMake script, are now all for the correct cpu architecture. (Only the *nix '.a' static libs were affected, but I'm committing new versions of all of the Windows VS2017 '.lib' files too in order to pick up the new "HHC01417I Built with..." version strings.)
Previously, I was distributing the VS2008 version since that's the version of Visual Studio that I use. But that causes problems for most others who try building Hercules for themselves since most everyone else uses VS2017 (and the VS2008 Debug static libs I was distributing won't work when trying to debug Hercules using VS2017; see GitHub Issues #104 and #106 for example).
Therefore I am now going to start distributing the *VS2017* version of the External Package static libs instead, which makes it much easier on most everyone else since now all they have to do is download Hercules and build it, PERIOD! They now no longer need to build any of the External Packages at all. I've already done that for them.
The burden is now on *ME* to build my own special VS2008 versions of the External Packages for myself, since I'm the "odd ball" that's still using VS2008 and not VS2017. (Why burden others with my own eccentricities after all?)
As of this commit it is no longer necessary to manually build the "Debug" version of any of the external packages if you wish to build a "Debug" build of Hercules. For both normal Release builds as well as for Debug builds, just build Hercules normally just like always.
Fish (David B. Trout)