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
next prev parent reply other threads:[~2020-07-28 3:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 6:18 My Guile Hacker Handbook Jérémy Korwin-Zmijowski
2020-07-23 6:46 ` test anything? (Re: My Guile Hacker Handbook) Marc Chantreux
2020-07-23 8:12 ` Frank Terbeck
2020-07-23 10:40 ` Jérémy Korwin-Zmijowski
2020-07-23 12:01 ` Marc Chantreux
2020-07-23 14:08 ` Jérémy Korwin-Zmijowski
2020-07-23 19:55 ` Zelphir Kaltstahl
2020-07-23 11:33 ` Marc Chantreux
2020-07-23 15:08 ` a French mailing list (was: test anything? (Re: My Guile Hacker Handbook)) Dmitry Alexandrov
2020-07-23 20:34 ` Marc Chantreux
2020-07-23 10:32 ` My Guile Hacker Handbook Bonface M. K.
2020-07-23 14:09 ` Jérémy Korwin-Zmijowski
2020-07-24 0:58 ` Bonface M. K.
2020-07-24 0:06 ` No Guile on Windows? (was: My Guile Hacker Handbook) Dmitry Alexandrov
2020-07-24 5:41 ` Eli Zaretskii
2020-07-24 7:22 ` Dr. Arne Babenhauserheide
2020-07-24 9:32 ` Christopher Lam
2020-07-24 11:50 ` Mike Gran
2020-07-24 16:25 ` Licensing of Cygwin comatibility layer (was: No Guile on Windows?) Dmitry Alexandrov
2020-07-24 23:33 ` Mike Gran
2020-07-24 14:00 ` No Guile on Windows? Ludovic Courtès
2020-07-24 14:20 ` Stefan Israelsson Tampe
2020-07-24 17:46 ` Dr. Arne Babenhauserheide
2020-07-24 17:47 ` Dmitry Alexandrov
2020-07-24 18:41 ` Jan Wielkiewicz
2020-07-25 3:48 ` No Guile on Windows? (was: My Guile Hacker Handbook) David Pirotte
2020-07-25 6:31 ` Eli Zaretskii
2020-07-25 13:56 ` Christopher Lam
2020-07-25 14:28 ` Eli Zaretskii
2020-07-28 2:52 ` Christopher Lam
2020-07-28 3:57 ` Mike Gran [this message]
2020-07-28 6:40 ` Vladimir Zhbanov
2020-07-25 16:49 ` Mike Gran
2020-07-25 16:33 ` Jérémy Korwin-Zmijowski
2020-07-25 21:38 ` No Guile on Windows? Dmitry Alexandrov
2020-07-24 6:47 ` No Guile on Windows? (was: My Guile Hacker Handbook) divoplade
2020-07-24 11:38 ` Stefan Israelsson Tampe
-- strict thread matches above, loose matches on Subject: below --
2020-08-13 13:02 Pikachu Hy via General Guile related discussions
2020-08-13 17:36 ` Linus Björnstam
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).