Hello All, I've fixed a couple typos and things from user feedback. I have also added several script control options that can decrease rebuild times if enabled. Below is a summary all the script control options and their function. All options are OFF (disabled) by default. You can view what is ON (enabled) in JTSDK-QT by typing: build-wsjtx -o
*enable-separate / disable-separate* - Separate Folders by App Version + SVN revision - Enable ....: wsjtx\devel\qt52\1.7.0\6362\Release\install - Disabled ..: wsjtx\devel\qt52\1.7.0\Release\install *enable-quiet / disable-quiet* - Enable or Disable additional on-screen messages where appropriate - This is similar to enabling verbose mode for the build script *enable-skipsvn / disable-skipsvn* - If Enabled, dont ask and dont update from SVN, just built it *enable-autosvn / disable-autosvn* - If Enabled, perform the SVN update without asking - Has no affect if skipsvn is enabled *enable-qt55 / disable-qt55* - Enable or Disable using QT5.5 as the Tool Chain *enable-clean / disable-clean* - Clean the build tree before cmake --build . - rconfig and dconfig do not use this option *enable-rcfg / disable-rcfg* - Re-run cmake configure before cmake --build . - rconfig and dconfig do not use this option When clean and rcfg is OFF (disabled), rebuild times are very short if a previous build is present. In the past, JTSDK cleaned and re-configured both the install and package targets. It is now up to the user which way to go. *UPGRADE* - To upgrade, if you have already switched to the cli-test branch, close all JTSDK windows, open a Windows CMD terminal again, then: cd /d c:\jtsdk set PATH=%PATH%;C:\JTSDK\subversion\bin svn update - If you are not on the cli-test branch, following the instructions from below. 73's Greg, KI7MT On 1/7/2016 17:59, Greg Beam wrote: > Hello All, > > I've added a testing / feature branch for JTSDK-Win Command Line Option > testing. See v2.0.4 Planned Updates message: > > http://sourceforge.net/p/wsjt/mailman/message/34742540/ > > Note, this upgrade uses a standard Windows CMD terminal, *Not* > JTSDK-Maint,PY,QT,MSYS or DOC. This is to avoid potential conflicts. > > Additionally, you *do not* use JTSDK-Maint (update and upgrade), rather, > simply follow the TEST-CONFIGURATION-SETUP below. Switching branches, by > default, updates to the latest in the respective branch. > > > *DISCLAIMER* > If your not well versed in command line FOO, you may want to wait for > the release of v2.0.4, however, most problems can be resolved with just > a few commands and there should be little risk to your current JTSDK > installation. > > > *UPDATES* > As updates and / or bugs fixes are resolved, they will be added to > ^/branches/cli-test, then later, when v2.0.4 is ready, the branch will > be reintegrated with the trunk and removed. At that point, users will > get switched to the new ^/tags/jtsdk-win-2.0.4 branch. > > There are a number of significant changes, but none should affect your > current Source, Install or Build Trees > > To enable / disable QT55, the command has changed to: > > enable-qt55 > disable-qt55 > > Along with this change, QT52 and QT55 builds are now separated into > their own folder locations. Pay close attention to the build messages, > as the output directories change a fare amount when enabling or > disabling options. The default is disabled, unless you previously had > QT55 enabled, in that case, qtenv will enable it for the new setup. > > When changing to / from QT55, remember to restart JTSDK-QT to ensure the > change takes affect properly. > > > *TESTING* > There are far too many combinations to list, so, simply test as many > combinations as you have time for or are willing to test. > > > *ERROR-REPORTING* > If you run into any issues, copy and paste the svn info from C:\JTSDK > directory along wiht the steps you took that can produce the error or > whatever the problem is. > > > *TEST-CONFIGURATION-SETUP* > - Open A Windows CMD terminal, *Not* JTSDK-Maint,PY,QT,DOC or MSYS > cd /d c:\jtsdk > set PATH=.;.\subversion\bin;.\tools\bin;%WINDIR%;%WINDIR%\System32 > > - Remove the following files to prevent possible conflicts. If you have > made > local changes to these files, copy them to a back up location first. > > del pyenv.cmd > del qtenv.cmd > del maint.cmd > > - Switch branches to cli-test. Note the double caret "^^/" is required > > svn switch ^^/jtsdk-win/branches/cli-test > > - Check svn info and verify your on the right branch: > > svn info |grep URL > > You should see the following: > > URL: https://svn.code.sf.net/p/jtsdk/jtsdk/jtsdk-win/branches/cli-test > Relative URL: ^/jtsdk-win/branches/cli-test > > - Close the Windows CMD Terminal. Open JTSDK-QT > - In JTSDK-QT, Generate the wsjtx-list files > > wsjtx-list -u > wsjtx-list -a > > - If there were no errors, display the build help screen > > build-wsjtx -h > > > *RESTORE-CONFIGURATION* > - Open A Windows CMD terminal, *Not* JTSDK-Maint,PY,QT,DOC or MSYS > > cd /d c:\jtsdk > set PATH=.;.\subversion\bin;.\tools\bin;%WINDIR%;%WINDIR%\System32 > > - Switch branches back to jtsdk-win v2.0.3 release > > svn switch ^^/jtsdk-win/tags/jtsdk-win-2.0.3 > > - Check svn info and verify your on the right branch: > > svn info |grep URL > > You should see the following: > > URL: https://svn.code.sf.net/p/jtsdk/jtsdk/jtsdk-win/tags/jtsdk-win-2.0.3 > Relative URL: ^/jtsdk-win/tags/jtsdk-win-2.0.3 > > - If you backed up any locally changed files, copy them back to C:\JTSDK. > > - Close Windows CMD terminal > > > That's all for now. If you have any problems, find typos, bugs whatever, > you can send them to me offline or to the list. > > > 73's > Greg, KI7MT ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
