Hi Bill, On 9/25/2014 17:20, Bill Somerville wrote: > On 25/09/2014 18:14, KI7MT wrote: >> HI Bill, > Hi Greg, >> >> On 9/25/2014 17:07, Bill Somerville wrote: >>> On 25/09/2014 17:50, KI7MT wrote: >>>> Hi Bill, >>> Hi Greg, >>>> On 9/25/2014 16:28, Bill Somerville wrote: >>>>> On 25/09/2014 15:39, Joe Taylor wrote: >>>>> Hi Joe, >>>>>> RR Bill, thanks for the update. >>>>> OK, I think I'm done. >>>>> >>>>> The Linux package building is still short of making compliant packages >>>>> but at least some sort of package (DEB and RPM) can be generated which >>>>> will at least install and run from in system directories (/usr) without >>>>> breaking anything AFAIK. >>>> The biggest thing I saw was the rigctld situation, which seems resolved >>>> now, at least for rc1 anyway. >>> Unless someone has an issue with it, I think shipping a hamlib 3 rigctld >>> called rigctld-wsjtx is just fine until the hamlib team get their v3 >>> release through all the hoops; given that AFAIK they haven't even >>> started that process yet, that will be quite some time into the future. >>> The need for rigctld-wsjtx is only for a very limited number of >>> specialized users and will not concern most WSJT-X users. >> I forgot to ask, is the Build External function working now or are you >> taking about shipping a pre-built bianry rigctld-wsjtx ? I been messing >> around on Windows and havn't built on Linux in a few days. > The super build project is not ready for use yet and will probably take > a while to get sorted out. > > The WSJT-X build process is basically the same on all platforms, hamlib > has to be built separately. Once that is done the WSJT-X CMake build > drags in the hamlib static archive library for linking into the wsjtx > executable and the rigctld built by the hamlib build. As part of the > install phase the rigctld executable is renamed to rigctld-wsjtx. Just > running the normal install or package targets on every platform does all > that is required.
Ok, I may have to write up a simple Makefile to first build hamlib, then WSJT-X to simplify the debian/rules file (the build script). This weekend is CQ WW RTTY Contest, but I'll try to get this done and working by Monday of next week. I think everything is ok on Windows now. Looks like Joe can build Hamlib3 and I have it working as well, so that can be updated for the -rc1 release if need be. Looks like John has things sorted out for Mac also. > > <snip> > > 73 > Bill > G4WJS. > > ------------------------------------------------------------------------------ > 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 > -- 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
