|
|
HAMLIB SDK Version 3Evolving the JT-ware Software Developer's Kit (JTSDK) |
|
|
| Installation | Build x64 | Build x86 | Developers | Notes | Questions | Sourceforge | Download |
This kit is a selection of packages focussing on building and compiling both Hamlib and JT-ware from their source GIT distribution repositories.
The software environments provided are much more powerful than just performing these roles. Full Qt-MinGW and MSYS2 environments are available for building software that can run under the MS Windows 10 + Operating System(s).
Examples for compiling key libraries needed by the JT-ware are provided in this section.
Eventually this kit will support the development of many more packages for Amateur Radio purposes.
The PowerShell environment offers a highly extensible environment basically for working with Qt and the JT-ware under the PowerShell environment.
There are extensive environment variables made available so that scripts like jtbuild can be created to build software.
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>
The MSYS2 environment offers a full MinGW/MSYS2 environment centred on building Hamlib.
Hamlib is not the only software that can be built here. Full MinGW32, MinGW64, CLang and UCRT64 environments can be launched that offer the GNU compiler suites and/or a deployed Qt-GNU compiler suite to develop software.
Software construction is moving away from using just the msys2 environment with the Qt compiler sets to develop software.
Techniques are evolving such that the mingw32 and mingw64 environments - with relevant packages added by the pacman tool - should be used to develop software that must be constructed using the GCC compilers.
---------------------------------------------------------------
BUILD-HAMLIB - HELP
---------------------------------------------------------------
* Available Command Line Options:
--> -h ........: Help
--> -b/-nb ....: Process / Do not process bootstrap
--> -c/-nc ....: Process / Do not process configure
--> -g/-ng ....: Process / Do not pull/check source from GIT repository
--> -libusb ...: Configure with LibUSB support
--> -nlibusb ..: Do not configure with LibUSB support
--> -static ...: Statically Linked Libraries built
or ..
--> -dynamic ..: Shared/Dynamically Linked Libraries built
* Note: You cannot select -static with -dynamic
If using switches you may need to combine options to over-ride default build behaviour:
i.e.: build-hamlib -nb reverts to Hamlib default STATIC build behaviour
build-hamlib -nb -dynamic over-rides this behaviour
radio@radio ~
$
Refer to the links below to see how some of the key JTSDK Libraries were constructed:
A very generalised development guide for software is available at:
The aim of JTSDK64-Tools is to use an Agile delivery approach to create a high-quality, yet flexible build system.
Base ref: https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-4.0-Stream/README.md
| Author: Steve VK3VM/VK3SIR | Contact |