[sword-devel] Win32 sword utilities for SWORD release 1.8.0 ?

[David Haslam]

Thanks, Greg.

Pretty sure I won't be the only person that uses Win32 editions of the utilities,
even I have occasionally put in a reminder whenever there's a new release. :)

As a Society, we should always remember that we are not a one platform outfit,
and that there are module developers and testers that do not have a pressing need to use Linux.

Best regards,

David

Sent with [ProtonMail](https://protonmail.com) Secure Email.

> -------- Original Message --------
> Subject: Re: [sword-devel] Win32 sword utilities for SWORD release 1.8.0 ?
> Local Time: 29 December 2017 9:11 PM
> UTC Time: 29 December 2017 21:11
> From: greg.hellings at gmail.com
> To: David Haslam <dfhdfh at protonmail.com>, SWORD Developers' Collaboration Forum <sword-devel at crosswire.org>
>
> You ask this every time there is an engine release and the answer is still the same: there are no official builds of the utilities for Windows. The only supported environment for running them is Linux and they are only supported when running from Subversion HEAD. Anywhere that they run outside of that is a happy accident.
>
> The fact that Karl's patch for diatheke was not included in Xiphos 4.0.7's release should not in any way surprise you. The patch would have been added, if it was  added, to the Subversion HEAD. Xiphos does not release against head but releases against Sword's official releases. If his patch was added, then it will be available when a version of Xiphos is released against Sword 1.8.
>
> I have, previously, released unofficial Win32 builds of the utilities solely to placate your repeated requests for them. Those are built out of the Fedora official build process (I sometimes will craft a build against pre-release versions of the engine, but I still use the Fedora release). In Fedora MinGW (win32 cross-build) environments we strive to keep the MinGW builds in lockstep with the native packages. I have not updated Fedora's native packages for 1.8 because the Python bindings were not compiling in 1.8.0. I've committed changes that enable that to compile and will release 1.8.1 with that change and any others that come through in the next few days. Although the Fedora MinGW builds do not build the Python bindings and should, therefore, not have a technical reason to wait for upgrading to 1.8 I am trying to keep with the MinGW guidelines to keep those packages as close to the native package as possible.
>
> When 1.8.1 hits the shelves, I will update Fedora 27 native and MinGW packages. At that point, I will create a tarball of those and drop it alongside where I normally put those packages on my download URL. I will be sure to let you know when I do that. But please, keep in mind, there is nothing official related to CrossWire in those builds, they are not supported by anyone other than myself, and there is no guarantee that they even will build (although there is no malice towards allowing them to continue building, and Troy and DM have generally accepted changes to keep them working when and if necessary).
>
> --Greg
>
> On Fri, Dec 29, 2017 at 11:48 AM, David Haslam <dfhdfh at protonmail.com> wrote:
>
>> If the Win32 sword utilities have already been compiled for SWORD 1.8.0 release, where can I find them?
>> If they are not yet made, please would someone do the honours. Thanks.
>>
>> btw. Was Karl's patch for diatheke -o M included ?
>> cf. Although he made the patch several months ago, it was not included in the win32 utilities distributed with Xiphos 4.0.7 (Windows edition).
>>
>> Best regards,
>>
>> David
>>
>> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20171229/86284d7b/attachment.html>