From: Mike Gran <spk121@yahoo.com>
To: Christopher Lam <christopher.lck@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 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: Mon, 27 Jul 2020 20:57:05 -0700 [thread overview]
Message-ID: <20200728035705.GA445483@spikycactus.com> (raw)
In-Reply-To: <CAKVAZZLmLDsHnUh_O0OGj88fiCryex7cRBAD2TpD7RGHTUpNdA@mail.gmail.com>
On Tue, Jul 28, 2020 at 10:52:47AM +0800, Christopher Lam wrote:
> 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
>
Yeah, that's a patched version of 2.2.7.
Even though I'm on a hiatus from coding, I believe I have all the
parts to make Guile 3.0.x work on MinGW 32-bit no-threads. Maybe I'll
just see if I can't put that together real quick.
-Mike Gran
prev parent reply other threads:[~2020-07-28 3:57 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 ` No Guile on Windows? (was: My Guile Hacker Handbook) Christopher Lam
2020-07-28 3:57 ` Mike Gran [this message]
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=20200728035705.GA445483@spikycactus.com \
--to=spk121@yahoo.com \
--cc=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).