From: Christopher Lam <christopher.lck@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-user <guile-user@gnu.org>,
help-guix@gnu.org, guile-devel <guile-devel@gnu.org>
Subject: Re: No Guile on Windows? (was: My Guile Hacker Handbook)
Date: Tue, 28 Jul 2020 10:52:47 +0800 [thread overview]
Message-ID: <CAKVAZZLmLDsHnUh_O0OGj88fiCryex7cRBAD2TpD7RGHTUpNdA@mail.gmail.com> (raw)
In-Reply-To: <83ft9fd5z2.fsf@gnu.org>
My mistake: gnucash uses MinGW-w64.
The gnucash lead developer has a few patches to successfully compile guile
on MinGW-w64. It would be great if these patches were taken upstream and a
CI pipeline enabled for testing. Otherwise gnucash for windows will always
need to catch up, and is at severe risk of falling behind.
https://github.com/jralls/guile
On Sat, 25 Jul 2020, 10:28 pm Eli Zaretskii, <eliz@gnu.org> wrote:
> > From: Christopher Lam <christopher.lck@gmail.com>
> > Date: Sat, 25 Jul 2020 13:56:28 +0000
> > Cc: guile-user <guile-user@gnu.org>, help-guix@gnu.org
> >
> > Gnucash 4.0 in windows is successfully using libguile-2.2-1.dll from
> MSYS2.
>
> Is Gnucash a MinGW build or an MSYS2 build? If the latter, it's
> expected.
>
next parent reply other threads:[~2020-07-28 2:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3364bc82b7660df3ae8613cdadef8b9dac2fe416.camel@korwin-zmijowski.fr>
[not found] ` <tuxxsrmq.dag@gnui.org>
[not found] ` <83wo2teag4.fsf@gnu.org>
[not found] ` <20200725004835.3e0c7056@capac>
[not found] ` <831rl0ds1e.fsf@gnu.org>
[not found] ` <CAKVAZZLiu3LyMb42qQnw0yG1WQBj9HxnByYNOF8aBGsxe-veuA@mail.gmail.com>
[not found] ` <83ft9fd5z2.fsf@gnu.org>
2020-07-28 2:52 ` Christopher Lam [this message]
2020-07-28 3:57 ` No Guile on Windows? (was: My Guile Hacker Handbook) Mike Gran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKVAZZLmLDsHnUh_O0OGj88fiCryex7cRBAD2TpD7RGHTUpNdA@mail.gmail.com \
--to=christopher.lck@gmail.com \
--cc=eliz@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).