v3.2.2
JTSDK Version 3.2.2 - Release
One thing that "scares the living daylights" out of the kit maintainers is the MSYS2 keyring issues re-surfacing - the very circumstances that led to the maintenance and work on the kits having to occur in the first place.
JTSDK64-Base-3.2.2.exe
Maintenance has been performed on the JTSDK64-Tools-Base-3.2.2.exe installer package (i.e. it is being bumped to Version u1) and anew Base package will be uploaded to both Sourceforge (the preferred delivery site) and GitHub when complete. Note: Please use Sourceforge as the primary download site as download stats are much easier to obtain from here. It also helps us to educate our community as most JT-ware in its documentation STILL refers to Greg KI7MT's great original work - yet that unmaintained work is now very troublesome for the community that we are aiming this at.
This maintenance update FULLY UPDATES the MSYS2 environment. It has Tools v3.2.2.3 pre-applied. If Tools v3.2.2.3 is applied to this it will effectively have no effect as it is already there - yet it is STILL advised to do this if this base installer is used due to some future plans that the team has. The latest PackageConfig (v1.8.0) is supplied but not activated yet in the Versions.ini file.
THERE IS NO NEED FOR ANY USER WITH A DEPLOYED JTSDK TO REAPPLY THIS PACKAGE.
The original release has been moved to Archive in case of issues. If you want this package please watch for it to appear at the top of the file list at https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/ as it is being upoaded as this notification is posted.
New deployments must use this revised package from this point forward.
JTSDK64-Tools 3.2.2.3.exe
A Tools 3.2.2.3 package - containing a number of significant fixes and improvements to the Base 3.2.2 Package - is now available for general distribution and use.
There have been a number of enhancements - including moving the VC Runtimes package to Version 17 i.e.versions that are compatible with Visual Studio 2022. The runtimes delivered are compatible back to Visual Studio 2017. This should overcome the "VC Runtimes Not detected" issue that some have experienced in the simplest way possible.
The path to the VC runtimes is now also configurable from Versions.ini .
The "NCD" (No Compiler Delivered) deploys are not affected by the files in the wrong locations. Yet this update should be applied if you have deployed the JTSDK this way.
If you have not deployed from the updated JTSDK64-Tools-Base-3.2.2.exe please deploy this update ASAP.
The Tools 3.2.2.3 release can be found at:
- https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/JTSDK64-Tools-3.2.2.3.exe
The Base package to which this Tools package is applied can be found at:
Deployment
The Tools 3.2.2.3 package only is guaranteed to work with the Base 3.2.2 Package.
To deploy the package follow these steps:
Install it into the same directory where the Base 3.2.2 Package is deployed.
This can be deployed over the top of any existing 'Tools' packages without deploying and preceding releases.
The very latest updates and tests can be found at: https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Tests
The equivalent of the "Tools" package plus any cutting-edge, up-to-the-minute updates are also available via GIT at the following URL's
- git://git.code.sf.net/p/hamlib-sdk/code
- https://github.com/hamlibdk/HAMLIB-SDK.git
Technically one could just "pull" the contents of these repositories over the top of existing deployment to get the very latest development kit version. At some stage in the future this may be the preferred way that Tools packages are deployed.
We welcome discussion on the best way to do this as the Developers admit not to being GIT gurus.
Please comment back and add your constructive comments to the review process.
JTSDK64-Tools 3.2.2.3-Package-Updates.exe
The JTSDK64-Tools 3.2.2.3-Package-Updates.exe package is just the Tools 3.2.2.3 package plus a number of updates to utilities and library suites that is available for testing.