Hello All,

Current CLI Branch Revision ..: 594

This update applies to WSJT and WSPR only (Python3 Versions).

Both WSJT and WSPR now utilize several command line options, similar to 
what is available with WSJT-X. In addition to the user defined options, 
you can also build any of the targets listed in the Makefile. Use [ 
build-(wsjt or wspr) list-targets ] to see what is available.

WSJT and WSPR do not use Debug and Release nor do they have multiple 
branches in ^/branches ^/tags ( devel / garc ) that can be built with 
the current JTSDK v2.0 tool set. If this changes going forward, the 
scripts can easily be updated to accommodate the selections.

Both WSJT and WSPR will now use: separate, quiet skipsvn, autosvn clean 
and autorun. They do not use, nor are they listed as available options 
in JTSDK-PY, qt55 or rcfg as those are exclusive to QT5 based applications.

Enable / Disable separate is slightly different than with WSJT-X for to 
the reasons listed above.

With Separate Enabled (WSJT or WSPR), paths would be:
-C:\JTSDK\{wsjt,wspr\{app-version}\{svn-revision}\{install,package}

With Separate Disabled (WSJT or WSPR), paths would be:
-C:\JTSDK\{wsjt,wspr\{install,package}

Both WSJT and WSPR build scripts also create their own InnoSetup ISS 
file. This allows for varying Version + SVN-Revision output locations 
based on enable-separate. You can still use the repository ISS files, 
however, you must disable-separate as the paths are hard-coded.

Both WSJT and WSPR still use AsciiDoc (Python27 dependent) as the markup 
language compiler. Before JTSDK-Win32 v2.0.4 and JTSDK-Nix v2.0.19 are 
released, both will need to be converted to Asciidoctor (Ruby 
dependent). Once this transition is complete, we'll no longer need 
Python27 or AsciiDoc for documentation builds.

For developers working on new features, upgrades or documentation, you 
will probably want to disable-separate as that keeps the installs, 
targets and documentation in line with the current JTSDK-Win32 v2.0.3 
output locations. When its time to test post-commits, simply 
enable-separate and the new revision will be isolated from the prevision 
revisions / builds.


*TO UPDATE or SWITCH*
- Switch to the cli-test branch see item [2] below,
- Update the cli-test branch, see item [3] below, upgrade section.


73's
Greg, KI7MT

THREAD HISTORY
[1] http://sourceforge.net/p/wsjt/mailman/message/34742540/
[2] http://sourceforge.net/p/wsjt/mailman/message/34748374/
[3] http://sourceforge.net/p/wsjt/mailman/message/34749028/
[4] http://sourceforge.net/p/wsjt/mailman/message/34749217/
[5] http://sourceforge.net/p/wsjt/mailman/message/34753479/

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to