I also got a Code 1 error at the completion of the XDft.sln build. It turns
out that my path for the downloaded (unzipped) XDwsjtFtSdkDir had a space in
the directory name. Once corrected the build was successful.
The process was a tad tedious but the features and functionality of DigiRite
are well worth it.
Many thanks to the Writelog team!
Jim, KS1J
-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of Steve
Lund
Sent: Saturday, October 12, 2019 00:07
To: Wayne, W5XD
Cc: Writelog Forum
Subject: Re: [WriteLog] DigiRite 1.1.32 update. and a new way to distribute
it
Well, I didn't have full success.
The XDft build ended with the following error:
The command "copy C:\digirite-build\binWin32\*.dll C:\Users\Steve
Lund\source\repos\Digi-Rite\Digi-XDft\Win32\Release\:VCEnd" exited with
code 1.
Not sure where the :VCEnd is coming from.
Typing this into a CMD prompt does work:
copy "C:\digirite-build\binWin32\*.dll" "C:\Users\Steve
Lund\source\repos\Digi-Rite\Digi-XDft\Win32\Release\"
Because most of the files are longer than DOS 8.3 quotes are need around
the directory paths.
The DigiRite build ended with the following error:
The command "copy C:\Users\Steve
Lund\source\repos\Digi-Rite\\Digi-XDft\Win32\Release\*.* C:\Users\Steve
Lund\Source\Repos\Digi-Rite\bin\x86\Release\" exited with code 1.
Note there are two "\\" in the first directory name; and again quotes are
needed around the directory paths.
Typing this into a CMD prompt does work:
copy "C:\Users\Steve
Lund\source\repos\Digi-Rite\Digi-XDft\Win32\Release\*.*" "C:\Users\Steve
Lund\Source\Repos\Digi-Rite\bin\x86\Release\"
Why am I experiencing these errors?
I was afraid to run Register.exe because of these problems. The
DigiRite.exe runs fine.
Steve, K6UM
On Wed, Oct 9, 2019 at 4:02 PM Wayne, W5XD <w5xd@writelog.com> wrote:
> To users of WriteLog with DigiRite
>
> There is a new version of DigiRite available. But...
>
> Since the previous release of DigiRite, version 1.1.30, we have received
> complaints from the WSJT-X copyright holders that the combination of
> WriteLog with DigiRite violates their software license, the Gnu Public
> License (GPL.) It is our reading that DigiRite does not violate the GPL,
> but our opinion does not remove the threat that we would have to pay
> lawyers to defend it. To reduce that threat to a level of risk we are
> willing to take (it cannot go to zero--anyone can sue anybody for
> anything in this country) we have removed the DigiRite installer kit
> from writelog.com. The DigiRite sources remain open (which is the
> primary requirement of the GPL after all) and are published on github
> and there are some new features since 1.1.30 that might interest you.
>
> These features are in version 1.1.32:
> 1. fix a bug that poorly chooses the priority of which messages to
> send to concurrent QSOs in progress.
> 2. Set the CQ message and the exchange to send in DigiRite dialogs
> rather than fishing around in WriteLog's f-key memories. (That was not a
> user-friendly choice in the first place, so its now fixed.)
>
> To get a running version of DigiRite 1.1.32, you have to build it
> yourself (or get someone to do it for you). The software tools are
> available for free download from Microsoft. The details are at
> http://writelog.com/digirite, which links to the build recipe here:
> https://writelog.com/digirite-build
>
> Wayne, W5XD
>
>
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|