Hello All, I've purposely been holding off on updating the Dev-Guide (which is dire need of attention!) until we had a build system in place and run through the mill to flush out major issues. If there's things needing attention in the build systems, please let me know and I can work on getting it sorted out.
While I have a pretty good system for note keeping, email archive :-), we sure could use a master TO-DO list somewhere, for core code things, new ideas, build systems, documentation systems, and just general items. Build Status As I know it to Be: WINDOWS - JTSDK-QT/PY ---------------------- WSJT-X: All Targets, Debug, Release, Package and RC's WSPR: All Targets + Packaging with Inno WSJT: All Targets + Packaging with NSIS MAP65: All Targets, Packaging needs looked at WSPR-X: All Targets, Packaging needs looked at * For MAP65 and WSPR-X, need to revisit copying files for Debug and test final packaging. Also need to get away from using appsupport and use the JTSDK-QT files to ensure consistency (e.g. hamlib, portaudio DLL's etc), and get all the binary files (libs and such) out of SVN and into the SDK. The CmakeLists.txt files for both WSPR-X and MAP65 need updating to use Bills Cmake Modules for finding dependencies like FFTW hamlib2, etc, ( another consistency item ). * Hamlib3, while this is a temporary situation, I believe we now have a build method to pull Bill's integration and build it on Windows. It has not been updated to mirror the specific RC version, but can be easily edit the pull the version you need to accompany a release candidate version. LINUX - JTSDK-NIX ----------------- Currently this only supports Ubuntu 14.04 and friends and the setup script needs a bit of work, but the base is functional. WSJT-X: All Targets, Debug, Release + RC build script WSPR: Builds and Performs System Install (Debian compliant) WSJT: Builds ok, but does not have an install target, needs work MAP65: Not functional, Cmakelists.txt needs updating WSPR-X: Builds and runs, but has many errors. Cmakelists.txt needs updating * We can easily build Hamlib3, either from JTSDK-NIX or the stand alone jtsdk-wsjtxrc.sh build script. * After updating the Dev-Guide, I was planning on updating WSJT to the same level as WSPR, then update Debian packaging to match. I have a TO-DO for this list if anyone is interested. * MAP65 is close, I the CMakeLists.txt needs updating for Find Modules, and a couple issues that fail during build. * WSPR-X, same as MAP65, it builds and runs, but it requortes a patch to fix poraudio as it set to find the windows DLL. * There are many build warning for both WSPR-X and MAP65. As such, JTSDK-NIX has these set to Under Development. DOCUMENTATION BUILDS: --------------------- * I think all the docs are building fine, both Windows and Linux. Data URI (single file build) is only available for Linux at the moment, but with JTSDK v2.0 I may be able to fix that when using an MSYS environment, but that is a ways out yet. That would also eliminate the Python27 need all together as MSYS uses Python26 which AsciiDoc will work with. * At some point, need to add a top level section that will allow us to build "All" WSJT documentation and create a Master Book ( tome ) that could be ported to ePub, DATA-URI or whatever format is wanted. -- 73's Greg, KI7MT ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
