On 08/06/2015 19:01, Jim Pennino wrote: Hi Jim, > I fully understand that, but: > > I can not find a download link for v 1.6 of any kind on either the wsjt site > or sourceforge > so even if I wanted to set up a development environment on a Windows machine > (or any > other machine) I couldn't do it. SourceForge is the source of the source code! We use a Subversion source control system hosted on SourceForge so not only can you get the source, you can get the latest source at any time. The clue is in the name ;) > > For v 1.5 I can find Linux source and instructions on how to build on a Linux > platform, > but nothing about the requirments for building on a Windows platform. We provide a source tarball when we make public releases, it can be used by anyone but the main recipients are Linux package maintainers who need a frozen version of what makes a release. > > Obviously all the above exists somewhere but there are no links to that > information that > I can find. Perhaps links on the wsjt development page like "for Linux, go > here, for Windows, > go here, for bleeding edge source, go here"? Greg KI7MT maintains a package for Windows (and Unix) called JTSDK which is for those less comfortable with setting up a development environment piecemeal. It contains all the tools and utilities pre installed along with a menu driven user interface to update your working copy of the source and to build the applications from it. Details of this tool and updates to it are regularly published on this list and other lists where WSJT-X, WSPR, WSJT, MAP65 and FMT users are found. > > By not having at least an occasional Windows "bleeding edge" package > available you > are missing out on a lot of potential testers. We do not build development packages for release, they are unstable and change faster than the time taken to build release kits. Also any published binary package implies some level of user support which we do not offer for development code.
Building cross platform applications on Windows is and always has been difficult due to the Microsoft proprietary way being so different from the accepted Standards like POSIX, but we make every effort to provide a route for those with the most limited of developer skills to participate. > > FYI I have been doing software development for over 40 years now and have no > problem > with building my own, if I can find the source. It's here: https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/ 73 Bill G4WJS. > > > > > -------------------------------------------- > On Mon, 6/8/15, Bill Somerville <g4...@classdesign.com> wrote: > > <snipped for brevity> > > We produce tools that allow non developers to build WSJT-X from source code > because > making many incomplete and unstable releases of development code is > non-productive. > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
