HAMLIB SDK Version 4 Evolving the JT-ware Software Developer's Kit (JTSDK)

Guide for Building x64 JT-Ware

Introduction

The scripts and packages provided assist with the construction of WSJT-X and derivatives JTDX and JS8CALL - collectively referred to as JT-ware.

These notes will assist with with techniques to build JT-ware

Note that the JTSDK 4.0.0 is x64/64-Bit Environment.

The PowerShell jtbuild commandlet

The PowerShell jtbuild commandlet is the scripted tool used to build JT-ware packages

jtbuild accepts the following options:

PS C:\JTSDK64-Tools> jtbuild -h	

--------------------------------------------
 Default Build Commands
--------------------------------------------

 Usage .....: jtbuild [ OPTION ] [[ SWITCH ]]

 Examples...: jtbuild rinstall
            : jtbuild rinstall -ng

 Options:

    rconfig    Release, Config Only
    dconfig    Debug, Config Only
    rinstall   Release, Non-packaged Install
    dinstall   Debug, Non-packaged Install
    package    Release, Windows Package
    docs       Release, User Guide

 Switches:

    Switches only work if an [ OPTION ] is supplied.

    -nc        Do not run configure
    -ng        Do not check/pull source

 * To Display this message, type .....: jtbuild -h

PS C:\JTSDK64-Tools>

Configuring which JT-ware package is auto pulled from source

A marker file placed in x:\JTSDK64-Tools\config determines which JT-ware package is downloaded and built:

PS C:\JTSDK64-Tools\config> dir


    Directory: C:\JTSDK64-Tools\config


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        23/07/2024  10:36 PM              0 hlmaster
-a----        23/07/2024  10:36 PM              0 qt5.15.2
-a----        31/08/2024   4:19 AM              2 src-jtdx
-a----         1/10/2024  11:51 AM            662 Versions.ini


PS C:\JTSDK64-Tools\config>

In thie example the JT-ware release set to be auto pulled from its source git repository is JTDX.

All valid entries for this marker file are:

• src-wsjtx - Pull and update WSJT-X from source (default)
• src-jtdx - Pull and update JTDX from source
• src-js8call - Pull and update js8call from source
• src-none - Custom build - Do not pull from source
• Note: The jtbuild -ng switch can over-rides any setting in x:\JTSDK64-Tools\config prevents any existing JT-ware source from being over-written/updated by any git process .

Changing repositories

To change from one repository all you do is rename the marker file in x:\JTSDK64-Tools\config to one of the valid options.

• i.e: (PowerShell command shown)

PS C:\JTSDK64-Tools\config> dir


    Directory: C:\JTSDK64-Tools\config


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        23/07/2024  10:36 PM              0 hlmaster
-a----        23/07/2024  10:36 PM              0 qt5.15.2
-a----        31/08/2024   4:19 AM              2 src-jtdx
-a----         1/10/2024  11:51 AM            662 Versions.ini


PS C:\JTSDK64-Tools\config> Rename-Item -Path ".\src-jtdx" -NewName "src-wsjtx"
PS C:\JTSDK64-Tools\config> dir


    Directory: C:\JTSDK64-Tools\config


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        23/07/2024  10:36 PM              0 hlmaster
-a----        23/07/2024  10:36 PM              0 qt5.15.2
-a----        31/08/2024   4:19 AM              2 src-wsjtx
-a----         1/10/2024  11:51 AM            662 Versions.ini


PS C:\JTSDK64-Tools\config>

Note: Multiple src-xxx marker files in x\JTSDK64-Tools\config

There can only be ONE prefixed src-xxx marker file in x:\JTSDK64-Tools\config .

Building JT-Ware

Procedure

Building JT-Ware under the x64 environment is a simple two-step process:

1. Build Hamlib
2. Execute the jtbuild command with an appropriate build option. (i.e. jtbuild package)

The Deployment Guide covers these steps in detail. Please refer to that guide.

Specific notes relating to building JT-ware packages can be found in the Application Notes Section.

Issues

Please refer to the Questions Section. Many answers will be found here.

Failing that please ask at the JTSDK Forum.