<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Apr 25, 2020 at 3:13 PM Karl Kleinpaste <<a href="mailto:karl@kleinpaste.org">karl@kleinpaste.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<font face="FreeSerif">I wanted to post something outside the
previous thread on building for Windows, in case folks had started
ignoring that one.<br>
<br>
Boy, ya mention a problem in need of attention, ya get some folks
motivated, and stuff just happens.<br>
<br>
<b>HUGE THANKS to Dom and Greg</b> for their efforts. I thought I
was in for a lot of grief and pain, trying to finish resurrecting
the Windows build. But as of the most recent merge, we have a
fully-automated Xiphos build for win32/64, driven by a Fedora30
container. All you need is to have </font><tt>podman</tt><font face="FreeSerif"> installed, plus a directory containing xiphos
and biblesync source directories, from which you issue this
command (courtesy of Dom).<br>
<br>
</font><tt>podman run -it -v .:/source fedora:30
/source/xiphos/win32/xc-xiphos-win.sh -win32 -win64
-b=/source/biblesync</tt><font face="FreeSerif"><br></font></div></blockquote><div><br></div><div>Worth noting that this also works with Docker. Literally just replace the "podman" with "docker" in the above command and the results are identical. That's how builds are being done automatically upstream, so we know it works, too.</div><div><br></div><div>The same script should be usable by anyone on a Fedora 30 machine/vm as well. I know Windows people are much more likely to have access to VMs than to Docker/Podman container environments so, with the same conditions as Karl mentions (a vm with Xiphos and Biblesync source checked out), call the xiphos/win32/xc-xiphos-win.sh script with the path to biblesync source updated appropriately.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><font face="FreeSerif">
<br>
It literally doesn't get easier than a single command to go from
bare source tree to completely constructed installers. You can add
"--rm" after "run" if you want to dispose of the container
afterward.<br>
<br>
At the moment, Xiphos is ahead of Sword in terms of certain
features, one of which will cause you annoyance in Bibles with
pre-book and -chapter material, including ESV (if you still have
it) and NASB. If you want to do any experimenting and building,
you should locally revert this change in your tree prior to
building:<br>
<a href="https://github.com/crosswire/xiphos/commit/74c88b94dc840d2e72d6a4ac974c0b3c56c42647.diff" target="_blank">https://github.com/crosswire/xiphos/commit/74c88b94dc840d2e72d6a4ac974c0b3c56c42647.diff</a><br>
If you're building for Linux, then you should build your own
Sword, the latest of which has the update addressed by this change
and you don't need to revert.<br>
<br>
I haven't yet actually taken the result to a Windows machine, but
under Wine it operates just fine as it always has.<br></font></div></blockquote><div><br></div><div>If anyone out there has a Windows machine but doesn't have the ability to build it themselves, the benefit of having the builds be automated is that you can get the build artifacts from the CI builds.</div><div><br></div><div>1) Go to this URL: <a href="https://github.com/crosswire/xiphos/actions">https://github.com/crosswire/xiphos/actions</a></div><div>2) Click on the build you want to test there (if you're looking to test someone's latest PR or other request)</div><div>3) Click on the link under artifacts called "packages"</div><div>4) Open the zip file and choose the installer you want to test</div><div><br></div><div>"Nightly" (e.g. per commit) builds of RPMs are coming in the near future, as well.<br></div><div><br></div><div>--Greg<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><font face="FreeSerif">
</font>
</div>
_______________________________________________<br>
xiphos-devel mailing list<br>
<a href="mailto:xiphos-devel@crosswire.org" target="_blank">xiphos-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/xiphos-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/xiphos-devel</a><br>
</blockquote></div></div>