Greetings, everyone:
As I'm working on my automation for Sword releases, one of the things that
people often ask for, despite all the advice against it, is Windows builds
of the utilities. For myriad reasons I'm not currently producing builds off
the head of Subversion, but rather from the latest
Greg:
Thanks. The Windows and Linux builds work fine in my testing for
osis2mod and xml2gbs and will incorporate in next major SwordHammer
release. Appreciate your making these available.
Tom
Tom Sullivan
i...@beforgiven.info
FAX: 815-301-2835
-
Great News!
God created
Thanks Greg,
I confirm that emptyvss is working in both suites.
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
On 12 February 2018 7:52 PM, Greg Hellings wrote:
> New files uploading now with that
New files uploading now with that util added.
--Greg
On Mon, Feb 12, 2018 at 1:31 PM, David Haslam wrote:
> Greg,
>
> *Further observation*.
>
> Neither suite includes the Sword utility *emptyvss.exe*
>
> Please rectify.
>
> Best regards,
>
> David
>
> Sent with
Greg,
Further observation.
Neither suite includes the Sword utility emptyvss.exe
Please rectify.
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
On 12 February 2018 7:28 PM, David Haslam wrote:
>
Thanks Greg,
This time, diatheke /? gave no errors and output the syntax help as expected.
This worked for both x32 and x64 editions.
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
On 12 February 2018 5:59 PM, Greg Hellings
On Mon, Feb 12, 2018 at 9:45 AM, David Haslam wrote:
> Thanks Greg,
>
> After downloading both 1.8.1 releases again, I tried the *x64* utilities
> and got this error message after entering
> *utils64\diatheke /?*
>
I've managed to dig out my Windows computer, so I've
Thanks Greg,
After downloading both 1.8.1 releases again, I tried the x64 utilities and got
this error message after entering
utils64\diatheke /?
[Screenshot 2018-02-12 15.28.13.png]
NB. I also tried your x32 utilities and got the same error message. i.e. After
entering
utils32\diatheke /?
On Mon, Feb 12, 2018 at 9:10 AM, David Haslam wrote:
> Greg,
>
> I refreshed http://dl.thehellings.com/sword-utils/
> in my browser, but the Zip files do not look more recent than 2018-01-30.
>
> Did you actually upload the updated Zip files?
>
I did, I just didn't
Greg,
I refreshed http://dl.thehellings.com/sword-utils/
in my browser, but the Zip files do not look more recent than 2018-01-30.
Did you actually upload the updated Zip files?
Best regards,
David
Sent with [ProtonMail](https://protonmail.com) Secure Email.
Original Message
On Tue, Jan 30, 2018 at 3:41 PM, David Haslam wrote:
> From a command window in the Sword path, I just tried *utils64\diatheke
> /?* and got the following message:
>
> [image: Screenshot 2018-01-30 21.33.04.png]
>
> FWIW, there is a DLL file with that name
From a command window in the Sword path, I just tried utils64\diatheke /? and
got the following message:
[Screenshot 2018-01-30 21.33.04.png]
FWIW, there is a DLL file with that name "libwinpthread-1.dll" installed with
Xiphos.
Best regards,
David
Sent with
On Tue, Jan 30, 2018 at 11:11 AM, David Haslam
wrote:
> Thanks Greg,
>
> I just downloaded *sword-utils-1.8.1-x86_64-release.zip* and created a
> symbolic link under my *sword path* to the extracted folder.
>
> It may be a while before I chance to try any of the utilities.
Thanks Greg,
I just downloaded sword-utils-1.8.1-x86_64-release.zip and created a symbolic
link under my sword path to the extracted folder.
It may be a while before I chance to try any of the utilities.
Are there any notes on what's different between the x32 and x64 builds ?
cf. My PC has
Dear all,
I have made a first pass at building the Windows version of the Sword
utilities. You can find the resulting builds for 1.8.1 here:
http://dl.thehellings.com/sword-utils/ as per usual.
These are not officially supported or endorsed by CrossWire. I create them
of my own volition and not
On 1/20/2014 5:18 PM, Greg Hellings wrote:
A few things are striking me as odd about the Windows build of the
utilities when compiling with Visual Studio Express 2013
1) Several utilities simply fail to run. Namely add* all bring up
Windows crash/error boxes immediately upon run with no output.
A few things are striking me as odd about the Windows build of the
utilities when compiling with Visual Studio Express 2013
1) Several utilities simply fail to run. Namely add* all bring up Windows
crash/error boxes immediately upon run with no output. Is this typical?
2) installmgr isn't
17 matches
Mail list logo