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

Guide for Building Boost

Introduction

As of JTSDK 3.2.2 Boost should ideally be built with the mingw64 environment.

Note that this is NOT the technique that the JTSDK64-Tools command Deploy-Boost uses.

These steps will demonstrate how to deploy a Windows MME-Interface-based driver.

If you want ALSA support – which requires a licensed SDK - refer to notes in the WSJT-X source.

Using the Deploy-Boost Script

This script, available from the JTSDK64-Tools console, can automate the entire process of building Boost. To use this script to properly build Boost there are some configuration changes to the environment that should be made first. The environment configuration setting unixtools= should be set to enabled inside Versions.ini.

This setting should be returned to disabled after you have built Boost.

• Using Windows File Manager, navigate to x:\JTSDK64-Tools\config.
• Right click on Versions.ini and select your favorite text editor or select 'Open' to edit the file.
• Locate the key unixtools=disabled. Change the line to unixtools=enabled.
• Save Versions.ini. Close any open JTSDK64-Tools environment Windows.

Note that the change will not be effected until all windows are closed and then re-opened.

Building from mingw64 Environment

Step 1: Download and fully deploy the latest JTSDK

• The JTSDK Version 3.4.1 and any Tools packages can be found at: https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.4-Stream/
• Refer to the Deployment Guide for deploying JTSDK 3.4.1.

Step 2: Deploy the Build Tools

The first stage involves deploying tools as if one were building Hamlib. Many required MSYS2 tools are deployed as part of this process. 

• Execute the following command inside the JTSDK-Tools environment:
• msys2
• Execute the following commands inside the MSYS2 environment:
• menu
• Select the following menu options:
• Select Option 2. to update the MSYS2 environment. If the environment requests that you close the window after completion then do so. Restart this section again.
• Select Option 3. Install Hamlib dependencies.
• Select Option 4. Install msys64 GNU Compilers.

This should have now downloaded the build environment for mingw64 – providing a POSIX-compliant environment in which Boost code should be built.

• Close all MSYS2 and JTSDK-Tools environment Windows

Step 3: Deploy the mingw64 Build Environment

Launch an environment with the native MSYS2 MinGW GNU compilers.

• If there were any JTSDK64-Tools environment windows in use please close them all now.
• Launch the JTSDK64-Tools environment
• Inside the JTSDK64-Tools environment launch the mingw64 environment:
• mingw64

Step 4: Download the Source

You need to determine the download URL of the latest stable Boost release by clicking on the “Current Release” link at https://www.boost.org/ . At the time of writing the current version was 1.85.0.

• Type the following commands:
• cd ~/src
• Right-click on the URL of the download file that you want – preferably the Unix .tar.gz file at https://www.boost.organd select “Copy Link”
• In the msys64 shell, type wget, paste the URL, and then press enter. i.e.
• wget https://github.com/boostorg/boost/releases/download/boost-1.85.0/boost-1.85.0.tar.gz

This downloads the source package.

• Extract the source package with:
• tar xvfz boost-1.85.0.tar.gz

Step 5: Configure and build the Boost libraries

Execute the following commands at the MSYS2 command prompt:

• cd boost-1.85.0
• ./bootstrap.sh
• b2 install --prefix=/tmp/boost

This places the built components into the subdirectory /tmp/boost. This way the libraries are easy to find.

Complete

You will find a structure inside /tmp (Windows path x:\msys64\tools\msys64\tmp\boost) that contains your built Boost library set that can be inserted into the JTSDK.

You will need to rename that folder to match the current version (i.e. rename folder  boost to 1.85.0) before it can be used with the JTSDK. 

Deliver that folder structure to X:\JTSDK64-Tools\tools\boost\ .

If you made adjustments to the key unixtools inside x:\JTSDK64-Tools\config\Versions.ini , set its value back to disabled.

• i.e. unixtools=disabled

Reference

• https://www.boost.org/doc/libs/1_63_0/more/getting_started/windows.html