Download Latest Version JTSDK64-4.0.0b1.exe (347.0 MB)
Email in envelope

Get an email when there's a new version of HAMLIB SDK (Evolved JTSDK)

Home / Windows / JTSDK-3.3-x86-Stream
Name Modified Size InfoDownloads / Week
Parent folder
Tests 2022-12-23
0
README.md 2022-09-25 15.5 kB
0
JTSDK-3.3.1-x86-EXPERIMENT.exe 2022-09-25 353.8 MB
0
Totals: 3 Items   353.8 MB 0

JTSDK64 Applications and Tools

JTSDK Version 3.3 Stream

The Version 3.3 stream is a learning, discovery and technique refinement experiment.

THIS IS JUST AN EXPERIMENT: Use the JTSDK 3.2 - Stream and x86 Patches for official x86 Builds

This experimental packages are not planned for release announcements.

Direction

The Version 3.3 stream evolves the JTSDK 3.2 kits further. The JTSDK 3.2 Stream evolved the JTSDK into PowerShell-based environments.

The Version 3.3 Stream evolves the kits basing deployment around Qt 5.15.2 working with MinGW 8.1 under the mingw64 MSYS2 environment. Earlier Qt versions (i.e. Qt 5.12.12 and MinGW 7.3) are no longer provided or supported.

In addition the JTSDK 3.4 Line will prepare for JT-ware Qt v6 development.

Release Notes: 3.3 Base Stream

There are no notes at this stage as this document is primarily just an anouncement that research and development has commenced.

Release Notes: Tools Package

It is still proposed at this stage to offer updates and enhancements in the form of "Tools" packages.

The Project needs contributors - Especially for management and to write Cross-Language Documentation !

Up To Date Documentation

It is not proposed to release any formal documentation at this stage for this experimental stream.

Refer to documentation included in the deployed package "Tools" tree.

It should be possible for JTSDK64-Base-3.2.2 and JTSDK32-3.3.1-x86 kits to co-exist and perhaps share non-library-based utility packages i.e. Use Windows Symbolic Links or Powershell Symbolic Links .

Release Status

This release is now at the Research phase of its life cycle.

Current packaging preempts known cases of proposed licence and delivery condition changes.

The "base" and recommended mainstream development environments will be Qt 5.15.2 and Boost-1.80.0 working with MinGW 11.2 under the mingw64 MSYS2 environment.

The Next Steps

Version 4 of the JTSDK will involve strategic re-think. Watch the JTSDK Forum for updates and to contribute.

Conventions used in this document.

Drive paths will be referred to as x:\ , where "x" is the default deployment drive i.e. x:\JTSDK64-Tools\config .

In most instances x:\ can be replaced with **c:\ **

Examples will mostly refer to **c:\ ** for clarity.

Kit Construction

To be advised.

Support

Heads-up advice from developers is essential. We are not 'enemies'; we are just inquisitive. Nobody asked us to do this - Nobody should have to ask in the AR community. Maintainers work on this to learn. We support the development of the skill base and hence reputation of Amateur Radio.

Added Support and Features

The Tests folder contains bleeding-edge efforts to translate and improve scripts.

Limitations

PowerShell scripts are managed to tight security rules. See the next section.

The kits may never be able to move away from the Windows CMD processor and its "Batch files" in order to compile JT-software. Even the PowerShell development environment needs to be launched through the WIndows CMD processor.

The Qt environment and its MinGW compilers and tools limit significantly some tasks that can be perfomed. At this stage no facility is available to add components as needed (as can be done with the MSYS2 environment with pacman ].

PowerShell Security Warnings

You may receive the following security notification:

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing 
the execution policy might expose you to the security risks described in the 
about_Execution_Policies help topic at https:/go.microsoft.com/fwlink/?LinkID=135170. 
Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"):

It is safe to select Y. These scripts are not any processor flaw tests. Remember that developing these scripts is also a learning exercise for the Development Team.

Windows Environment Variables

The basic concept of supporting Windows Environment Variables through PowerShell $env:<env-var> facilities that ease access into CMAKE, QMake and the MinGW compilers will remain a cornerstone concept.

Upgrades

There are no current *Tools packages.

Before any updates (manual from "Tests" or from a "Tools" package) you should backup your MSYS2 Environment:

  • Copy any folders stored under x:\JTSDK32-Tools\tools\msys64\home to a backup location. This should enable you to access previous work.
  • Close any open MSYS2 environment terminal(s).
  • Perform the system upgrade.
  • Delete folders that exist under x:\JTSDK32-Tools\tools\msys64\home.

i.e: PowerShell: ** Remove-Item "C:\JTSDK32-Tools\tools\msys64\home*" -Recurse -Force **

Note: The src directory in your backup should contain your previous work. It is safe to copy this enture foler across to your new MSYS2 Profile.

You will need to pull down your Hamlib repository again and/or restore any custom work to folders created within the MSYS2 environment.

Deployment

Preparation: Deploy a Virtualisation Environment

Do not deploy this release onto base systems.*

It is recommended to deploy the JTSDK into a fresh Windows Virtual Machine. For those unfamiliar with "Virtual Machines" and "Virtualisation Technologies" you shoud refer to https://www.redhat.com/en/topics/virtualization/what-is-virtualization .

** Note:** Almost EVERY CPU that Runs Windows x64 these days has virtualisation support.

If you have concerns please refer to https://www.technorms.com/8208/check-if-processor-supports-virtualization .

There are lots of virtualisation environments available. Click on the links below to obtain details on how to deploy these systems:

Trial Virtual Machine images for Windows 10 (with Microsoft's Compiler Suite) can be downloaded from https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/ . These Virtual machines should have a lifetime of at least 30 days.

Contributions

How Can I Help?

Please test these scripts and those in the Tests folder. Report observations either via the JTSDK Forum or the email address where most most messages come from (if you cannot post). The JTSDK Forum is used somewhat as as 'blog' as information in there is too valuable for the general IT community.

The 'core team' behind this are not PowerShell gurus. This is a learning effort. If you are a PowerShell guru PLEASE PLEASE PLEASE jump in and comment to assist. Send back BETTER SCRIPT. Teach us all.

We especially require people to make these README.md scripts better !

** ALL CONTRIBUTIONS AND COMMENTS ARE GRATEFULLY WELCOMED ** !

Bug Reports

For submitting bug reports and feature requests, use the Issue Tracker.

Reports, suggestions and comments via the JTSDK Forum - or via the email addresses from main contributors there of late if you do not have post access - are essential.

Conclusion and Further References

The aim of JTSDK32-Tools is to provide experimental environment, using an Agile delivery approach, to create a high-quality, yet flexible build system.

Base ref: https://sourceforge.net/projects/jtsdk/files/win64/3.1.0/README.md

Source: README.md, updated 2022-09-25