[sword-devel] sword-build-win32 - New automated solution for building the latest SWORD dll (+deps) for Windows

[Troy A. Griffitts]

Well, that's great news, Tobias, all around! Of course, I'm most happy you can't reproduce the problem you reported! 🙂 I will fix the link error. This symbol should just be moved out of the header file and anonymously namespaced in the cpp file. I'll try to have a look a bit later today.

Thanks for the great progress! I'll leave it to you and Greg to work out the logistics of if he wants to adopt your work for his official builds, move it to our build server running Jenkins or translate it to build services on our Gitlab, or leave it on GitHub as-is and simply point there for our official windows build. Release management and CI is his pumpkin. I trust he will find your progress extremely useful. I would be interested to know if your build has the UTF-8 filesystem pathname issues we've experienced with other compilers and if Xiphos and Bibletime can link to your dll for their windows builds.

Thank you! Blessed Sunday,

Troy

On February 16, 2020 10:39:58 AM MST, Tobias Klein <contact at tklein.info> wrote:
>Hi all,
>
>In an attempt to improve the Sword build process for Win32 I’ve
>automated this now, using the GitHub actions functionality.
>https://github.com/tobias-klein/sword-build-win32
>
>This repository links to the SWORD dependencies (CURL, ICU, etc.) in
>the form of Git submodules. It also links SWORD (using the Git mirror
>from BibleTime) as a submodule.
>
>I’ve set up automatic build scripts, which means whenever one of the
>versions (of either Sword or any of its dependencies) in the scripts
>has been changed and pushed back to GitHub a new build will be
>automatically created. When a release is published, the corresponding
>release binaries (dlls) are automatically generated and the current
>SWORD headers are also included in the release zip file. The zip file
>(containing the libraries and headers) is then automatically attached
>to the release page on GitHub. The compiler used to build the
>dependencies and SWORD itself is Visual Studio 2019.
>
>An example is the current „development release“ 1.8.900-2020-02-16.
>https://github.com/tobias-klein/sword-build-win32/releases/tag/v1.8.900-2020-02-16
>
>I’m using these auto-generated binaries now for the Windows build of
>node-sword-interface, the SWORD backend of Ezra Project (before I was
>using manually generated Windows binaries that I created a year ago).
>
>There is one odd thing that I had to do when linking against the
>sword.dll. I had to include the following snippet in
>node-sword-interface:
>char * sword::SWBuf::nullStr = (char *)"";
>For some reason this symbol is stripped out of sword.dll and unless I
>add it in the software that links against sword.dll I get a linker
>error …
>I already needed to handle this issue when building Sword for Windows
>manually one year ago.
>
>Best regards,
>Tobias
>
>PS:
>@Troy
>For some reason I couldn’t observe the recently described crash anymore
>in this most recent build.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200216/00d78ca6/attachment.html>