A number of operators using WSJT-X 1.7.0 have been voicing their frustrations at being unable to download an installer for WSJT-X 1.7.1. Joe Taylor K1JT explains the position of the Development Team as follows: "We're now at a stage where tests under a wider range of conditions are desirable. If you can build WSJT-X from source code revision r7750 or later, and would like to help, please do so and report your results to us! Pre-built installation packages will be made available after further testing is completed.
Past experience has taught us how best to optimize our development procedures for significant program additions or upgrades. Important steps in our sequence are roughly as follows:
1. Early tests using simluation software
2. On-the-air tests among ourselves

3. We ask those who can "build their own" (from the publicly available source code) to try it out and provide feedback.
4. When all seems to be working well, we polish the code for best efficiency, update the documentation, and make a "candidate release".
The next one will be called wsjtx-1.8.0-rc1: (Version 1.8.0, Release Candidate 1. Pre-built installation packages will be provided for Windows, Linux, and OS X.
5. We fix bugs and polish the user interface and the User Guide. If deemed necessary, we make additional candidate releases, say -rc2, -rc3, or whatever.
6. When all seems well, we make a full General Availability release.

We are currently at Step 3 in the above sequence. If you want to join the other Step 3 testers, you have two obligations: build the program yourself, and provide thorough, detailed feedback about your experiences
and any bugs that you discover. This means keeping up-to-date with bug fixes along the way, paying attention to repository log messages, etc.
Experience has shown us that free-for-all access at "Step 3" is counter-productive in many ways. Far too many "free-loaders" download the package, play on the air with what might be buggy software, provide
no useful feedback, and sometimes give new program features a bad name before they are even finished.
Also important: at this point in the development of a new mode, some characteristics of the mode may be still in flux. We don't want lots of
unauthorized, unreleased programs in the field that will cause later backward-compatibility issues.
So, once more... Please Be Patient."

Fortunately for those of us with limited understanding of compilers and source code, Greg Beam KI7MT has done most of the work for us by making available his JTSDK suite. This is a set of tools that allow even someone with minimal understanding of Command-Line program execution to create their own, up-to-date WSJT-X release. Be warned though, a couple of these files are BIG!

Below I have outlined IN DETAIL the procedure to follow in order to create your own Build (and future Builds). I would also seriously recommend joinging the wsjtgroup Yahoo Mail Reflector.


Click the following links to download.

When all files are downloaded, install them IN THAT ORDER. Please be aware - the Main Installer is 682Mb and Update-2 is 634.5Mb. The first 2 files are Microsoft Runtime Libraries - these MAY already be installed in your system, in which case installation can be skipped. If you already have Omnirig installed, there is then no reason to install it again - your existing configuration will not be affected. JTSDK WILL install itself to C:/JTSDK - this is not changeable. Please note that an Internet connection is necessary throughout the installation, as considerable content is downloaded from Sourceforge and other sources.

Once installation is completed there will be a numer of Icons on the desktop - JTSDK-DOC, JTSDK-MSYS, JTSDK-PY and JTSDK-QT.

After the installation finishes, and before building Hamlib3 or other autotools applications:

XP / Vista / Win7

Win8 / Win10

After installation, you need to set a few options first.
Open JTSDK-QT, then type each of these commands, followed by "enter"

enable-autorun (this is optional, but will run the build if it completes)

Close, then reopen JTSDK-QT

The Hamlib development team recently made a slight change to their build invocation. As result, a minor change to the JTSDK-Win Hamlib3 build script was required.
* Open JTSDK Maintenance
* Type: update
* Type: upgrade
* Close, then reopen JTSDK Maintenance
* Type: version

You should now be on v2.0.6-0 Release 710

Now to build : at the JTSDK-QT prompt, type:


The hamlib3 build IS quite lengthy - on an i5 processor-based PC it should take around 10 minutes - this is unavoidable.
Now build WSJT-X : here you can either build a ready-installed package (if you enabled autorun above, it will pop open automatically upon completion) or you can create your own installer (generically named wsjtx-1.7.1-devel-win32.exe).
The command options are as follows:

build-wsjtx rinstall

build-wsjtx package

Upon completion the JTSDK-QT window will show the location of the compiled files.

Each time you change QT version, you should build hamlib3 again, just to make sure it's fresh and built with the correct tool chain.

That is all there is to it!!  To build new versions as changes are announced, simply repeat the "build" commands in JTSDK-QT. Remember to always rebuild hamlib3 BEFORE building new versions of WSJT-X.