Bill, No. I feel that you are not correct based on past posts that both you, Joe and other key developers have made. Directions are clear that Greg KI7MT's JTSDK 3.0 is the standard environ for Windows. Yet 64 bit Windows builds are also appearing on Joe's release site - and the JTSDK 3.0 cannot do this.
The JTSDK 3.0 "build-hamlib.sh" MSYS2 script pulls the latest HAMLIB GIT repository from your site. Most of us are using the "standardised" methods first and before anything else and any other project/sdk i.e. the 3.1 "experiment".... although it's the 3.1 experiment that is drawing out more-and-more issues that are primary related to advancement of libraries and tools. Yes I know that you release an "standardised" version of Hamlib with the WSJT-X source. But that is not the point. Amateurs here want the best along with the best support possible for their transceivers (i.e. the latest Hamlib etc). that many of you great developers out there are working on. I personally need some of these contemporary Hamlib fixes to support hardware that I work on or hardware that I customise software for. As examples, your HAMLIB code especially has shifted to better support many of the Yaesu and Kit-SDR radios that I use and work with. There is no advancement of Amateur Radio continuing resistive discussion. If you forensically compare JTDX code to WSJT-X code you will note the required changes that have crept in for some time into that project's codebase. Can I also please request that in any further codebase release that you specify in the easily accessible README / INSTALL etc. the build environ (library packages needed, code, packages, versions etc.) that the codebase is standardised to? This also makes access, learning and experimentation into configuring SDK's for development easier (and that is what HAM Radio is about). This also makes YOUR life easier as when things do not work you can specify that people go back to the standardised development environ (i.e. Greg KI7MT's JTSDK 3.0 is the current standardised Windows environment). I feel that it is time for another release as a considerable amount of time has progressed since the last release. Many packages (i.e. Qt) have advanced and for the better. Likewise quite a number of key developers and testers on the WSJT-X project (as well as JTDX) are PM'ing me - suggesting that this and that changes that I refer to appear to have been made already. Many Amateurs are making the same requests of me/to me in PM's to me but are too frightened to ask in here as they often see others getting their heads bitten off making simple, reasonable requests or asking simple questions. Yet Bill as always I highly value and follow your advice and the advice that everyone offered in posts. Thanks for responding :-) [ We are HAMs ... we must collectively change that attitude by being very considerate in our responses and be tolerant of repetition and "newbies" .... hence quashing the fear to ask and hence learn. ] No High Court / Supreme Court Arguments here Bill .... Just simple and reasonable requests that ADVANCE AR :-) 73 Steve I VK3VM/VK3SIR _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
