From: KI7MT <ki...@gm...> - 2016-04-14 22:52:30
|
Hi Richard, See below. <snip> > > What does jtsdk look for when there is already an earlier version of wsjtx built ????? > maybe something which will give more problems in the future Greg. There are various JTSDK v2.0.20 options that affect rebuilds after a large System Wide update as you described. On the JTSDK Main Menu, select Options >> Option Status or from the command line, simply type: jtsdk -h or jtsdk -l That will show the options you have enabled. Options of interest are: separate ( seperate build by svn revision ) clean ( clean the build tree before rebuilding ) rcfg ( re-runs the configure step before building ) quiet ( enabled additional on screen messaging ) You can enable / disable each of the options separately, via command-line or the menu system. Enabling separate, at a minimum, will separate each build by svn revision number. It may not have mitigated the issue you were seeing, however, if a commit was made between the time you upgraded and the time you rebuilt WSJT-X, it would have created a new build tree, possibly overtiring the issue altogether. Enabling the above options will slow the build down, however, it will ensure a new / clean build tree each iteration. Generally speaking, disabling the options above are for Core Developer who are working on a specific element and need quick re-builds time. For me, and most general users / testers, enabling the options help overt strange things happing between build(s) and system package updates. <snip> 73's Greg, KI7MT |