Hi Mike, Bill, In the past JTSDK used to perform a clean on the build tree every round. Now, based on suggestions from Bill and others, in order to decrease build times for developers, the default is to *not* perform the clean.
As you noted Mike, it is very easy to enable / disable cleaning the build tree when needed. These changes were enabled starting at the v2.0.3/4 point with the addition of command line options. When JTSDK v3 is released, unless there is a pressing need to keep QT 5.2 around, QT5.5 / 5.6 will be the default. I'll no doubt be in discussion with Bill and Joe before hand to determine the appropriate requirements. 73's Greg, KI7MT On 4/4/2016 09:49, Michael Black wrote: > Yes...JTSDK does use separate build trees. That's why I'm not sure > how he got the qt5 path in the qt55 build tree. Must've been some > interim state when qt55 was being worked on. > Nonetheless...he's fixed. > > I've been using JTSDK since the early days....I do believe it used to > do a clean every time until somewhat recently. > I don't recall if i set disable-clean or if it was in an update. Guy > doesn't remember ever doing disable-clean and I know for a fact my > system was doing complete builds at one time so I think it changed at > some point not too long ago. > > RRR > Mike W9MDB > > > > On Mon, Apr 4, 2016 at 10:41 AM, Bill Somerville <g4...@classdesign.com> > wrote: >> On 04/04/2016 16:29, Michael Black wrote: >>> I guess JTSDK has changed the default to disable-clean? >> Hi Mike, >> >> definitely yes! Doing unnecessary clean builds is a huge waste of time. >> OTOH some configuration changes, particularly upgrading prerequisite >> packages, occasionally does need a fresh build tree and even a clean >> target will not sort it out even though CMake usually works out for >> itself that a reconfigure is required and everything needs rebuilding. >> >> I tend to reserve the clean target for saving disk space on build trees >> that I rarely use. >> >> In general, build time linking errors and run time linking errors like >> the one Guy was seeing are a good time to scrap and restart the build >> tree unless you know there is a specific link error due to some code >> change. This is stuff that developers suffer and become used to >> diagnosing, the JTSDK does make it easier to build but it doesn't make >> you a developer ;) >> >> I was under the impression that the JTSDK-QT used separate build trees >> for Qt 5.5 based builds. >> >> Related to this, I don't see any reason not to use Qt 5.5 on Windows - >> it is what is used for official packages until 5.6 is a bit more stable. >> >> 73 >> Bill >> G4WJS. >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> 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 > ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
