Op donderdag 25 april 2019 23:54:01 CEST schreef John Ralls: > Updated via > https://github.com/Gnucash/gnucash-on-windows/commit/c739d231 > (commit) from > https://github.com/Gnucash/gnucash-on-windows/commit/fe22df60 (commit) > > > > commit c739d231b5dc4775d40433d3148979a4a4d4c7ab > Author: John Ralls <jra...@ceridwen.us> > Date: Thu Apr 25 14:53:28 2019 -0700 > > Guile 2.2 for Windows. > > diff --git a/gnucash.modules b/gnucash.modules > index 04c3856..29b8c62 100644 > --- a/gnucash.modules > +++ b/gnucash.modules > @@ -119,11 +119,9 @@ > </autotools> > > <!-- Unfortunately in addition to needing a few patches this hangs when > it tries to compile Scheme. --> > - <autotools id="guile2" > autogen-sh="autoreconf" autogenargs="--without-threads"> > - <branch > repo="ftp.gnu.org" module="guile/guile-2.0.14.tar.gz" - > version="2.0.14"> > - <patch > file="https://raw.githubusercontent.com/Gnucash/gnucash-on-windows/master/p > atches/guile-2.0.14-mingw64-fixups.patch" strip="1"/> > - <patch > file="https://raw.githubusercontent.com/Gnucash/gnucash-on-windows/master/p > atches/guile-2.0.14-Fix-mktime-test.patch" strip="1"/> > + <autotools > id="guile2" autogen-sh="configure" autogenargs="--disable-rpath > --enable-networking --enable-nls --enable-posix --enable-regex > --with-threads --with-modules --disable-static"> > + <branch > repo="sourceforge" module="gnucash/Dependencies/guile-2.2.4+mingw.tar.bz2" > + version="2.2.4+mingw">
I am aware I suggested on irc to put the tarball on sourceforge. However while seeing this commit I wonder if there's a reason not to do as we did for guile 2.0: start from the upstream tarball and apply patches during the build ? That would mean storing the patches in our gnucash-on-windows repo. Geert _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
