From: David Pirotte <david@altosw.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andrewgoh95@yahoo.com.sg, guile-devel@gnu.org
Subject: Re: Implementing Guile with a Windows port
Date: Sat, 9 Oct 2021 22:02:06 -0300 [thread overview]
Message-ID: <20211009220206.311a3127@aicha> (raw)
In-Reply-To: <83h7dqrqvc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Le Sat, 09 Oct 2021 21:32:23 +0300,
Eli Zaretskii <eliz@gnu.org> a écrit :
> > From: Taylan Kammer <taylan.kammer@gmail.com>
> > Date: Sat, 9 Oct 2021 20:10:15 +0200
> >
> > I can't speak for the developers, but as far as I can tell, there
> > isn't the right combination of willingness and resources to support
> > a native port of GNU Guile for MS Windows.
> >
> > As far as I know, there's a MinGW port, but if I'm not mistaken
> > it's partly neglected and not as feature-rich as the "normal"
> > GNU/Linux version.
>
> A MinGW port of Guile 2.0.11 can be found on the ezwinports site.
> AFAIK, the only feature it omits is threads, because Guile built with
> threads is broken on MS-Windows.
Fwiw, when I need to, I use msys2:
https://www.msys2.org/
https://packages.msys2.org/search?t=binpkg&q=guile
=>
Package Version
guile 2.2.7-1
libguile 2.2.7-1
libguile-devel 2.2.7-1
Not sure it has all 'native' features, but it has threads.
hth,
David
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-10-10 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1994873807.737861.1633780908082.ref@mail.yahoo.com>
2021-10-09 12:01 ` Implementing Guile with a Windows port Andrew Goh
2021-10-09 18:10 ` Taylan Kammer
2021-10-09 18:32 ` Eli Zaretskii
2021-10-10 1:02 ` David Pirotte [this message]
2021-10-10 6:29 ` Eli Zaretskii
2021-10-10 16:25 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
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=20211009220206.311a3127@aicha \
--to=david@altosw.be \
--cc=andrewgoh95@yahoo.com.sg \
--cc=eliz@gnu.org \
--cc=guile-devel@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).