wsjt-devel

[wsjt-devel] JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

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] Update-1: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

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

Re: [wsjt-devel] Update-2: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@ya...>]

Hello All,

I've had a several questions asking about svn checkouts for the various 
WSJT-X branches and what has changed in the cli-test branch. For he 
benefit of all, I'm posting to the list rather than individually.

For anyone using using the ^/cli-test branch checkout-<app-name> is no 
longer used for WSJT-X builds.

If the branch your trying to build does not reside within C:\JTSDK\src, 
the build script will perform the checkout automatically, assuming 
things are OK with your Internet connection and SF is functional. This 
is true for all branches listed in: wsjtx-list -a.

Bare in mind, all WSJT-X branches in ^/branches and ^tags that can be 
built with QT5.2+ can now be built with one script and you no longer 
need to use build-wsjtxrc or build-wsjtxexp. These scripts (-wsjtxrc, 
-wsjtxexp) are still present in the ^/scripts folder, but will be 
removed once the formal release is made.

Subsequent SVN updates / rebuilds are controlled as they were in the 
past, either manually with Y/N when asked, or now with one of the svn 
control options, enable-autosvn / enable-skipsvn

All other apps, WSPR, WSJT, MAP65 and WSPR-X still use the 
checkout-<app-name> method. This will change as their builds scripts are 
updated.

If you experience any problems with the new checkout / control method, 
please post them to the list.


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/

Re: [wsjt-devel] Update-2: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

Hello All,

I've had a several questions asking about svn checkouts for the various 
WSJT-X branches and what has changed in the ^/cli-test branch. For the 
benefit of all, I'm posting to the list rather than individually.

For anyone using using the ^/cli-test branch, checkout-<app-name> is no 
longer used for WSJT-X builds.

If the branch your trying to build does not reside within C:\JTSDK\src, 
the build script will perform the checkout automatically, assuming 
things are OK with your Internet connection and SF is functional. This 
is true for all branches listed in: wsjtx-list -a.

All WSJT-X branches in ^/branches and ^/tags that can be built with 
QT5.2+ can now be built with one script and you no longer need to use 
build-wsjtxrc or build-wsjtxexp. These scripts (-wsjtxrc, -wsjtxexp) are 
still present in the ^/scripts folder, but will be removed once the 
formal release is made.

Subsequent SVN updates / rebuilds are controlled as they were in the 
past, either manually with Y/N when asked, or now with one of the svn 
control options, enable-autosvn / enable-skipsvn

All other apps, WSPR, WSJT, MAP65 and WSPR-X still use the 
checkout-<app-name> method. This will change as their builds scripts are 
updated.

If you experience any problems with the new checkout / control method, 
please post them to the list.


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/

[wsjt-devel] Update-3: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

Hello All,

Current CLI Branch Revision ..: 591

First, thanks to all those testing the cli-test branch, it's helped me 
resolve several issues rather quickly.

I've now worked through the WSJT-X build script update list I had. One 
major change for this round is, you can now build / update Hamlib3 
directly from within JTSDK-QT *without* having to open JTSDK-MSYS.

* To Build Hamlib3 via JTSDK-QT
- Open JTSDK-QT
- Type ..: build-hamlib3

This will open an MSYS Bash terminal and call the hamlib3 build script 
directly, then exit the shell when complete. Look and feel is similar to 
that of build script SVN checkout / updates, but it takes much longer to 
run. The outputs should track with having QT55 enabled or disabled.

Other Minor Updates:
* Fixed an issue with WSJT install target
* Add List Options command to JTSDK-QT / PY
* Consolidated help files
* Removed unused wsjtxexp and wsjtxrc build scripts
* Updated checkout-<app-name> commands / script
* Added a runtime Batch file for WSJT-X Debug Install target
* Removed all Ask Run prompts, use enable-autorun instead
* Added enable-autorun / disable-autorun
- When enabled, WSJT-X will automatically start after a successful 
Install Target build ~ no more typing long paths or being prompted to 
run the build, just run it or not.

Next on the TO-DO list is to enable the user config options for the 
remaining build scripts (WSJT, WSPR, MAP65 and WSPRX). I've already 
started updating the WSJT and JTSDK-PY env.

*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/

[wsjt-devel] Update-4: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

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/

[wsjt-devel] Final Update: JTSDK-Win CLI Branch Available For Testing

[Greg B. <ki...@gm...>]

Hello All,

This is the final update regarding the CLI Test branch.

I've finished working on all the major items in ^/cli-test and have 
reintegrated the branch back into the trunk. No further updates will be 
made to this branch.

Following the reintegration, I've created a devel branch 
^/jtsdk-win-2.0.4 which will be used to create the Final v2.0.4 Tagged 
Release once all the last minute items have been take care of.

For those using the ^/cli-test branch, you should shift over to the 
devel branch. The Release Notes will be updated to include this change.

* Open JTSDK-Maint, then type:

update
svn switch ^^/jtsdk-win/branches/jtsdk-win-2.0.4

* Exit & Re-Open JTSDK-Maint, verify version information, type:

version

* Check to ensure your on ^/branches/jtsdk-win-2.0.4

-----
* Version: JTSDK-Win32 v2.0.4 Devel
* Last Changed Rev: 617
* URL: 
https://svn.code.sf.net/p/jtsdk/jtsdk/jtsdk-win/branches/jtsdk-win-2.0.4
* Last Changed Date: 2016-01-19 23:02:49 -0700 (Tue, 19 Jan 2016)
------


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/
[6] http://sourceforge.net/p/wsjt/mailman/message/34760723/