Alex, Back in the days of WSJT (ie. before WSJT-X) the code relied on a proprietary Reed-Solomon code (KVASD) which Joe was permitted by the copy-right holders to incorporate into WSJT but only as a binary. I first ported WSJT to a Mac and Joe would login to my Mac and build a KVASD binary for me so that I could build WSJT releases for the Mac community. In those days two OS’s existed: Microsoft Windows and Apple Macs.
Now times have moved on - there are more OS systems than can be counted. The previous arrangement when Joe/Uwe can login to another computer and build binaries is impractical - possibly impossible. I can understand why this choice (closed code) has been made because of the non-collegiate actions of others. The question is how to propagate binaries in a trusted way - perhaps involving particular distributors (eg Debian, M1/2/3) to have source code on an agreed and trusted basis. — John G4KLA
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
