On 26/03/2014 15:07, Joe Taylor wrote:
Hi Bill, Greg, and all --
Hi All,
Congratulations to Bill on finishing (nearly?) a monumental job! Your
new code will mark a big step forward for WSJT-X.
Let's hope so.
Similar congratulations to Greg, for his recent work on JTSDK, a
self-contained WSJT software development kit for Windows. I am
already finding these tools to be a big help in building and
maintaining WSJT, WSPR, MAP65, WSJT-X, and WSPR-X. I'll be posting
download links on the WSJT web site very soon.
The combination of Bill's new code and Greg's new tools enabled me to
build and run a WSJT-X version that calls itself "WSJT-X 1.4.0, local"
within a few minutes after Bill's r3929 commit -- essentially "out of
the box".
That's good news. You do need to make a couple of changes to your
environment as documented in my last post but it appears they are not
absolutely essential for a basic build.
More precisely: on the first go, after entering "build wsjtx" in
Greg's C:\JTSDK-QT environment, CMake complained that it could not
find the hamlib library (as Bill had expected). As a temporary
measure, I copied an existing libhamlib.dll.a into the ...\src\wsjtx
directory. CMake then ran to completion, and WSJT-X was alive.
OK, that is a bit of a hack but sort of gets things going. I assume you
already had OmniRig installed on your machine.
The only other message of note was
"Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)"
I suppose this is because it wants to find CPack, and that's not yet
in the JTSDK-QT package?
That message can be ignored, the CMake code to find Hamlib starts by
using pkgconfig but on Windows that is a lost hope so it reverts to
searching the CMAKE_PREFIX_PATH. PkgConfig is part of the GNU packaging
tools and is supposed to include details of how to build against a
library as part of the library installation.
Bill, would it make sense for now to include your Windows
libhamlib.dll.a in the svn repository? This would mean that others
can build a WSJT-X that should behave in Windows as yours does. We
can do it in a more conventional way after the hamlib changes have
been released.
I'm still not sure how to proceed with this one. Obviously at some point
in the future Hamlib will make an official release with the Hamlib-3
library (which is what is in their repo master branch and my fork). At
the moment we are in a double transnational phase with the Hamlib
release to come and some of my changes to hamlib pending. I don't want
to put anything firm into the build system just yet.
I have built a Windows hamlib kit and put it here:
https://dl.dropboxusercontent.com/u/4192709/Hamlib-integration-wsjtx.tgz
or here for those that don't have tar and gzip available:
https://dl.dropboxusercontent.com/u/4192709/Hamlib-integration-wsjtx.zip
You will need to unpack it somewhere and include the path to
.../hamlib/mingw32 inside it in your CMAKE_PREFIX_PATH instead of any
prior Hamlib library you were using. Note that the separate Hamlib back
end libraries are now gone, the Hamlib team have decided to build one
monolithic library for the whole lot which IMHO is a good thing.
One feature of the new CMake build is that it now fixes up RPATH in both
the build area and the install area. Along with the new data file
locations and the in-executable resource packaging this means that you
can test the program by running it in the build tree as well as teh
install tree.
About JTSDK:
The present plan is to put links to three self-extracting windows
executables on the WSJT web site:
JTSDK-DOC.exe 3 MB - for building our asciidoc-based manuals
JTSDK-PY.exe 93 MB - for building WSJT and WSPR
JTSDK-QT.exe 458 MB - for building MAP65, WSJT-X, and WSPR-X
These packages will surely continue to evolve, but they are already
*very* usable and *very* convenient. I am using them now for all
Windows-based builds.
Those for MAP65, WSJT-X, and WSPR-X are all done with CMake. Currently
builds of WSJT and WSPR are driven by Windows *.bat scripts and use
makefiles.
For others who may wish to use the JTSDK tools: some instructions and
download links will be available very soon -- possibly even later today.
Final comment: after some delay for unknown reasons, I finally got
word that the wsjt-devel subscribers list will soon be transferred to
a new list at SourceForge. I hope we can transfer these
communications to that list very soon.
-- 73, Joe, K1JT
73
Bill
G4WJS
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
