[GNC-dev] broken build dependencies within Gnucash on Windows project

[John Ralls]

Dale,

Downgrading Guile isn't an option, unfortunately. Guile 2.0 has a serious design flaw reading UTF8 strings on Windows. Just be patient, I'll have the build fixed soon. I've actually settled on a solution and you can locally patch your guile-2.2.4+mingw source to get going again: Just '#ifndef __MINGW32__' the definition of mtkime() in lib/mktime.c.

A big part of the delay is that I decided yesterday to use 'make dist' to make a new tarball of guile from the patched repo instead of just tarring up the repo like I did last month. It's still grinding away 16 hours later. 

Regards,
John Ralls



> On May 28, 2019, at 6:20 AM, Dale Phurrough <dale at hidale.com> wrote:
> 
> John, as I'm invested to get a Windows build pipeline working (even for stable gc 3.5), I volunteer to fork the gcow 🐄 repo on github and try a few changes. Its easy for me to iterate/test.
> Asking/volunteering so that we both don't do the same work. [caveat: I will not fix guile, instead downgrade to the prev version that matches the existing patch]
> 
> --Dale
> 
> On Mon, May 27, 2019 at 9:39 PM Geert Janssens <geert.gnucash at kobaltwit.be> wrote:
> On maandag 27 mei 2019 21:22:47 CEST John Ralls wrote:
> > What I don't see much point in attempting to build is GnuCash 3.1 using the
> > exact same dependencies as those in the release bundle. Although you could
> > get partly there with the built dependencies, you'd also need to set up the
> > MinGW64 packages to what was on the build server that day.
> > 
> Yeah, that's a fair point indeed...
> 
> > The jwbuild-based build system never built 2.6.x or earlier; that was the
> > old system I cleaned out a couple of weeks ago.
> > 
> > You're right and I'm wrong about patches directories, at least according to
> > the docs. I'll try changing to relative paths after I get Guile beaten back
> > into submission.
> 
> Nice!
> 
> Geert
> 
>