|
![]() ![]() |
Installation | Build x64 | Build x86 | Developers | Notes | Questions | Sourceforge | Download |
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.
The script Deploy-Boost is available from the JTSDK64-Tools console and automates the process of building and deploying Boost.
These processes here describe how to build and deploy Boost without the use of the Deploy-Boost tool.
Execute the following command from the JTSDK64-Tools console:
Note that the change will not be effected until all windows are closed and then re-opened.
The first stage involves deploying tools as if one were building Hamlib. Many required MSYS2 tools are deployed as part of this process.
This should have now downloaded the build environment for mingw64 – providing a POSIX-compliant environment in which Boost code should be built.
Launch an environment with the native MSYS2 MinGW GNU compilers.
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.
This downloads the source package.
Execute the following commands at the MSYS2 command prompt:
This places the built components into the subdirectory /tmp/boost. This way the libraries are easy to find.
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.
Editor: Steve VK3VM/VK3SIR | Contact |