Hello All, I setup a few Windows Tasks an Linux crons to do nightly builds for all five WSJT apps. I test each application manually (except MAP65, as I don't have an SDR) for basic RX/TX functionality. I leave one or two running over night. On Windows, the apps are built with the JTSDK's, Bash scripts for Linux. On Linux, Hamlib2/3 is built from Bill's (G3WJS) hamlib integration files, and I use his binaries for Windows. Linux build scripts are not ready for release yet.
All builds are from whatever the latest SVN has, so if the build fails, that should be expected (could be build script related also), as the Developers are constantly adding things to the repos. *JTSDK-QT BUILDS* *WSJTX* - Builds with Cmake. - Bill updated the wsjt.pro to an Makefile.MinGW to allow for QtCreator + Qmake builds so traditional methods be ok now. - JTSDK-QT builds both Debug & Release versions, default is Debug. With the Debug Version, you must use the pre-built wsjt.bat file to launch it as this provides the needed paths to FFTW, Hamlib, QT5 and tool-chain files. - The Release version on Windows is slow, so be prepared. This is a Windows objdump issue, not a build / application problem. Expect upwards of 3 to 5 minutes for a full build to complete. - Initial testing on Linux is good, when Hamlib2/3 files are built locally. - Lots of cool new stuff to checkout!! *WSPR-X * - Builds with Cmake. - Is still using Hamlib 1.2.15.3. I tested with Bill's Hamlib2/3 binaries, and it's running, but the CMakelists.txt file needs updating to accomidate this, as do the JTSDK-QT build scripts, so I added an additional jtsdk-toolchain1.cmake file to use the supplied Hamlib binaries for now. - I tried building with QtCreator and Qmake. Had problems with .pro and Makefile.MinGW. - For Linux, there's a hard code to usb0 link causing issues, adding local mods gets around this. Long term, this should probably be updated in the repos when Hamlib2/3 is released. - Overall, it's running good. *MAP65* - Builds with CMake - I can't really test this one much, but it builds an launches. Looks pretty cool. Maybe the SDR users can give this one a shot. *JTSDK-PY BUILDS* *WSJT* - Updated the main build script for F2PY not found errors, and everything works after updating / creating the wsjt.ini file. - Have not tested much on Linux, as I'm still working through the deps. *WSPR* - Also updated the build scripts for F2PY. - Builds nicely. I have one issue, related to the hamlib-yaesu.dll from (1.2.15.3 binaries). If I copy a new version into \wspr\bin, all is well. No other problems to speak of. *JTSDK-DOC* - All documents build with: build [document name ] To launch the document in your default browser, type [document name ] *Example*: build wsjt wsjt - Builds then launches wsjt do in your default browser. That's all for now, if you run into trouble, send into the dev-list. 73's Greg, KI7MT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
