You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p>The <strong>JTSDK 3.2.3</strong> evolves the kits from Windows Batch Files towards Windows
55
+
<p>The <strong>JTSDK 3.4.0</strong> evolves the kits from Windows Batch Files towards Windows
56
56
<ahref="https://docs.microsoft.com/en-us/powershell/">PowerShell</a>-based scripts. <ahref="https://docs.microsoft.com/en-us/powershell/">PowerShell</a> is also supported in Mac and
57
57
Linux environs, so common-adaptation for these purposes may occur as the kits evolve. </p>
58
58
<p>This started as an experiment to reduce maintenance (i.e. new package versions).
@@ -65,15 +65,15 @@ <h3>The Version 3.2 Base Stream</h3>
65
65
<ul>
66
66
<p>The <strong>Version 3.2</strong> stream is a learning, discovery and technique refinement experiment. </p>
67
67
</ul>
68
-
<h3>Version 3.2.3</h3>
68
+
<h3>Version 3.4.0</h3>
69
69
<ul>
70
-
<p>The <strong>JTSDK 3.2.3</strong> outwardly will appear similar to the <strong>JTSDK 3.2.0</strong>-stream. Yet the
71
-
<strong>JTSDK 3.2.3</strong> has significant enhancements in that many of the key commands now accept
70
+
<p>The <strong>JTSDK 3.4.0</strong> outwardly will appear similar to the <strong>JTSDK 3.2.0</strong>-stream. Yet the
71
+
<strong>JTSDK 3.4.0</strong> has significant enhancements in that many of the key commands now accept
72
72
switches that can make the process of developing code quicker and simpler.</p>
73
73
<p>In addition the "mirroring" of <strong>build-hamlib.sh</strong> and <strong>build-hamlib.sh-static</strong> has been
74
74
broken - with <strong>build-hamlib.sh</strong> offering a number of additional command-line switches to
75
75
aid developers.</p>
76
-
<p>The <strong>JTSDK 3.2.3</strong> provides a version of <ahref="https://libusb.info/">LibUSB 1.0.26</a> that we have supplied. LibUSB 1.0.26 as supplied by the LibUSB maintainers is still supplied.</p>
76
+
<p>The <strong>JTSDK 3.4.0</strong> provides a version of <ahref="https://libusb.info/">LibUSB 1.0.26</a> that we have supplied. LibUSB 1.0.26 as supplied by the LibUSB maintainers is still supplied.</p>
77
77
</ul>
78
78
79
79
<tablewidth="*" align="center" border="1">
@@ -92,12 +92,12 @@ <h3>Project Status</h3>
92
92
build libraries (i.e. <ahref="https://www.boost.org/https://www.boost.org/">Boost</a>) as part of the learning process.</p>
93
93
<p>Current packaging preempts known cases of proposed licence and delivery condition changes. </p>
94
94
95
-
<p>Precompiled drop-in packages for <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.74.0-MinGW-v7.3-v8.1.7z">Boost-1.74.0</a>, <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.81.0-MinGW-v8.1-v11.2.7z">Boost-1.81.0</a> and <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.82.0-MinGW-v8.1-v11.2.7z">Boost-1.82.0</a> built under Qt's <ahref="http://www.mingw.org/">MinGW</a> 8.1 and <ahref="http://www.mingw.org/">MinGW</a> 11.2 environs are available (saving 3+ hours).</p>
95
+
<p>Precompiled drop-in packages for <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.74.0-MinGW-v7.3-v8.1.7z">Boost-1.74.0</a>, <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.81.0-MinGW-v8.1-v11.2.7z">Boost-1.81.0</a>, <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.82.0-MinGW-v8.1-v11.2.7z">Boost-1.82.0</a> , <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.83.0-MinGW-v8.1-v11.2.7z">Boost-1.83.0</a> and <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.84.0-MinGW-v8.1-v11.2.7z">Boost-1.84.0</a> built under Qt's <ahref="http://www.mingw.org/">MinGW</a> 8.1 and <ahref="http://www.mingw.org/">MinGW</a> 11.2 environs are available (saving 3+ hours).</p>
96
96
</ul>
97
97
98
98
<tablewidth="*" align="center" border="1">
99
99
<tr>
100
-
<tdclass="custd"><p>The recommended mainstream development environments are <ahref="https://www.qt.io/download-open-source">Qt</a><strong>5.15.2</strong> and <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.82.0-MinGW-v8.1-v11.2.7z">Boost-1.82.0</a> working with <ahref="http://www.mingw.org/">MinGW</a><strong>8.1</strong>.</p></td>
100
+
<tdclass="custd"><p>The recommended mainstream development environments are <ahref="https://www.qt.io/download-open-source">Qt</a><strong>5.15.2</strong> and <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/Boost-1.84.0-MinGW-v8.1-v11.2.7z">Boost-1.84.0</a> working with <ahref="http://www.mingw.org/">MinGW</a><strong>8.1</strong>.</p></td>
Copy file name to clipboardExpand all lines: docs/ver3/DG3-Build-Boost.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ <h2>Building from mingw64 Environment </h2>
74
74
<h3>Step 1: Download and fully deploy the latest JTSDK i.e. v3.2.3</h3>
75
75
<ul>
76
76
<li>The JTSDK Version 3.2.3 and any Tools packages can be found at: <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/">https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-Stream/ </a></li>
77
-
<li>Refer to the <ahref="DG3.html">Deployment Guide for deploying JTSDK 3.2.3</a>.</li>
77
+
<li>Refer to the <ahref="DG3.html">Deployment Guide for deploying JTSDK 3.4.0</a>.</li>
Copy file name to clipboardExpand all lines: docs/ver3/DG3-Build-x64-JT-ware.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ <h3>Introduction</h3>
51
51
<ul>
52
52
<p>The scripts and packages provided assist with the construction of <ahref="https://www.qt.io/download-open-source#section-2>Qt</a>-based environment are provided that enable <a href=" https:physics.princeton.edupulsark1jtwsjtx.html>WSJT-X</a> and derivatives <ahref="https://jtdx.tech/en/">JTDX</a> and <ahref="http://js8call.com/">JS8CALL</a> - collectively referred to as <strong>JT-ware</strong>.</p>
53
53
<p>These notes will assist with with techniques to build JT-ware</p>
54
-
<p>Note that the <strong>JTSDK 3.2.3</strong> is by default a x64/64-Bit Environment. </p>
54
+
<p>Note that the <strong>JTSDK 3.4.0</strong> is by default a x64/64-Bit Environment. </p>
<p>The scripts and packages provided assist with the construction of <ahref="https://www.qt.io/download-open-source#section-2>Qt</a>-based environment are provided that enable <a href=" https:physics.princeton.edupulsark1jtwsjtx.html>WSJT-X</a> and derivatives <ahref="https://jtdx.tech/en/">JTDX</a> and <ahref="http://js8call.com/">JS8CALL</a> - collectively referred to as <strong>JT-ware</strong>.</p>
53
-
<p>These notes will assist with with techniques to build JT-ware.</p>
54
-
<p>Note that the <strong>JTSDK 3.2.3</strong> is by default a x64/64-Bit Environment. Patches are maintained by <ahref="https://www.qrz.com/db/dg2ycb">Uwe Risse DG2YCB</a> that will enable the kit to be <strong>modified to build x86/32-bit software</strong>.</p>
55
-
</ul>
56
-
<hr/>
57
-
<h2>Patching the JTSDK 3.2.3 x64 environment to build x86</h3>
58
-
<hr/>
59
-
<ul>
60
-
<p>A complete section of the <ahref="https://sourceforge.net/projects/hamlib-sdk/">Hamlib SDK SourceForge Repository</a> is dedicated to maintaining patches and instructions for techniques that can be applied for enabling x86 builds.</p>
61
-
<p>These instructions can be found within the following folder: <ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-x86-Patches/">https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-x86-Patches/</a>.</p>
62
-
</ul>
63
-
<h3>Step 1</h3>
64
-
65
49
<ul>
66
-
<p>This tutorial is about how to add 32-bit build support to JTSDK64-Tools. It works for version 3.2.3.</p>
67
50
68
-
<p><strong>Ensure that you have a functional version 3.2.3 of JTSDK64-Tools in place.</strong></p>
69
-
70
-
<p>For all further steps I assume that you installed it to <strong>C:\JTSDK64-Tools</strong> and that you are familiar with how to use the JTSDK64. If you use another directory, adjust the paths accordingly.</p>
71
-
</ul>
72
-
<h3>Step 2</h3>
73
-
<ul>
74
-
<p><ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-x86-Patches/Files%20for%2032-bit%20support%20%28for%203.2.0.x%29.zip">Download the zip file from Sourceforge</a> and move the contained files to the following locations (replace the old files):</p>
<p>Copy the latter 3 files also to <strong>C:\JTSDK-Tools\tools\msys64\etc\skel\bin.</strong></p>
89
-
</ul>
90
-
<h3>Step 3</h3>
91
-
<ul>
92
-
<p>Start the Qt Maintenance Tool. </p>
93
-
<p>Download and install at least one 32-bit version of Qt (e.g. 5.15.2) as well as CMake_32.</p>
94
-
<p>The correct location for Qt is <strong>C:\JTSDK64-Tools\tools\Qt</strong>, and the Qt Maintenance Tool automatically generates a sub-directory <strong>C:\JTSDK64-Tools\tools\Qt\Tools\CMake_32</strong>. </p>
95
-
</ul>
96
-
<h3>Step 4</h3>
97
-
<ul>
98
-
<p>To be ready for building x86 compilations, we need only a few additional packages:</p>
<p>Adjust the entries in Versions32.ini to those version numbers you have installed.</p>
116
-
</ul>
117
-
<h3>Step 6</h3>
118
-
<ul>
119
-
<p>Have in mind that the 64-bit part of <strong>JTSDK64-Tools</strong> gets its information from <strong>Versions.ini</strong>, and the newly added 32-bit part from the file <strong>Versions32.ini</strong>, so that you can have different settings for making x86 and x64 compilations. Also the internal sub-locations are different for 64-bit and 32-bit. </p>
120
-
<p>The new 32-bit part doesn’t interfere with the existing 64-bit part of JTSDK64.</p>
121
-
</ul>
122
-
<h3>Step7</h3>
123
-
<ul>
124
-
<p>Now it’s time to start the work with your new 64+32-bit supporting JTSDK64-Tools…</p>
125
-
</ul>
126
-
<h3>Step 8</h3>
127
-
<ul>
128
-
<p>Start<strong> jtsdk64-setup.ps1</strong> and wait until setup is completed.</p>
129
-
</ul>
130
-
<h3>Step 9</h3>
131
-
<ul>
132
-
<p>For 64-bit compilations start<strong> jtsdk64.ps1</strong> as you are familiar with. Everything should work as before. Only the layout of the UI has been slightly optimized, so that it looks the same as for the 32-bit part. </p>
51
+
<p><strong>Note</strong>: This is not supported directly. Use the <strong><ahref="https://sourceforge.net/projects/hamlib-sdk/files/Windows/JTSDK-3.2-x86-Patches/\">Version 3.2 Stream</a> kits and notes there. </strong></p>
<p><strong>Note:</strong> To be able to distinguish the 32-bit part from the 64-bit part, the term “JTSDK32” instead of “JTSDK64” is used in the new 32-bit part of your JTSDK64.</p>
138
-
</ul>
139
-
<h3>Step 11</h3>
140
-
<ul>
141
-
<p>Start <strong>msys2</strong>.</p>
142
-
<p>The msys2 layout now offers you shortcuts for the various options. You simply have to type the right shortcut number and press ENTER to build hamlib.</p>
143
-
<p>Use shortcut “5” to build a fresh 32-bit version of hamlib into <strong>C:\JTSDK64-Tools\tools\hamlib32</strong> directory.</p>
144
-
145
-
</ul>
146
-
<h3>Step 12</h3>
147
-
<ul>
148
-
<p>Once hamlib32 has been built, close the <strong>msys2</strong> terminal window.</p>
149
-
</ul>
150
-
<h3>Step 13</h3>
151
-
<ul>
152
-
<p>Now it’s time to put a suitable wsjtx folder into the well-known location (<strong>C:\JTSDK64-Tools\tmp</strong>\) .</p>
153
-
</ul>
154
-
<h3>Step 14</h3>
155
-
<ul>
156
-
<p>Open again <strong>jtsdk32.ps1</strong> and start the x86 compilation of wsjtx with the command <strong>jtbuild32 package</strong>.</p>
157
-
</ul>
158
-
<h3>Step 15</h3>
159
-
<ul>
160
-
<p>The output directory is <strong>C:\JTSDK64-Tools\tmp\wsjtx-output32</strong>, so that is does not interfere with the 64- bit compilations.</p>
161
-
<p>In case you get an error message “asciidoctor is required to build the documentation”:
162
-
<ul>
163
-
<li>Open a terminal window</li>
164
-
<li>Go to <strong>C:\JTSDK64-Tools\tools\ruby\3.0.3_32</strong></li>
<p>This installs the <strong>Asciidoctor</strong> package.</p>
167
-
</ul>
168
-
<p>Now compilation of 32-bit builds should work.</p>
169
-
</ul>
170
-
<h3>Step 16</h3>
171
-
<ul>
172
-
<p>In case a 64-bit compilation starts instead of building for x86, check whether there is any symbolic link on your computer which leads to the 64-bit version of MinGW. (Such links are usually on <strong>C:\</strong>).</p>
173
-
<p>Delete all such links.</p>
174
-
<p>Now, both<strong> jtsdk32.ps1</strong> and<strong> jtsdk64.ps1</strong> should find the right build environment automatically.</p>
175
-
</ul>
176
-
<h3>Complete !</h3>
177
-
<ul>
178
-
<p>Enjoy your new 32-bit build support!</p>
179
-
</ul>
180
-
181
-
<hr/>
182
-
<h2>Notes for building x86 WSJT-X</h3>
183
-
<hr/>
184
-
<ul>
185
-
<p>There are no special notes for building <strong>WSJTX</strong> at this time.</p>
186
-
<p>Source for <strong>WSJT-X</strong> and <strong>JTDX</strong> is development prioritised for any build process.</p>
187
-
</ul>
188
-
189
-
<hr/>
190
-
<h2>Notes for building x86 JTDX</h2>
191
-
<hr/>
192
-
<ul>
193
-
<p>There are no special notes for building <strong>JTDX</strong> at this time.</p>
194
-
<p>Source for <strong>WSJT-X</strong> and <strong>JTDX</strong> is development prioritised for any build process.</p>
195
-
</ul>
196
-
<hr/>
197
-
<h2>Notes for building x86 JS8CALL</h2>
198
-
<hr/>
199
-
<ul>
200
-
<p>There are no special notes for building <strong>JTDX</strong> at this time.</p>
201
-
<p>Source for <strong>WSJT-X</strong> and <strong>JTDX</strong> is development prioritised for any build process.</p>
202
-
</ul>
203
-
<hr/>
204
-
<h2>Notes for working with your own modified source</h2>
205
-
<hr/>
206
-
207
-
<ul>
208
-
<p>Modify the source for your own requirements at your own peril.</p>
209
-
<p>Ensure that you comply with the source release requirements and terms for <strong>WSJT-X</strong> - again at your own peril.</p>
210
-
<p>If uncertain as to what these requirements are then please ask in the <strong>WSJT-X Forum</strong></p>
0 commit comments