From: Mike Gran <spk121@yahoo.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: Re: [EXT] Guile 64-bit Windows support, redux
Date: Tue, 6 Jun 2023 21:58:24 +0000 (UTC) [thread overview]
Message-ID: <1223010247.378529.1686088704626@mail.yahoo.com> (raw)
In-Reply-To: <CAJ=RwfaKYGJ4k9mEWd87Mev-_OcZtkwXWEgWk_D+JVfQrggZTQ@mail.gmail.com>
On Tuesday, June 6, 2023 at 02:10:25 PM PDT, Thompson, David <dthompson2@worcester.edu> wrote:
...
>> Janneke has also poked at Windows support a few times as well, and
>> he actually got it to run on 64-bit Windows.
>Did JIT work? When I tried this years ago it didn't. Would be a major
>victory if it works now.
There were patches that made it compile, but, I don't think it ever
properly worked. I always build without JIT.
I haven't tried to build with JIT in a while.
...
> I'm obviously not a maintainer but I do want to be vocal in my support
> for a good Windows story. Despite how much I personally do not want
> to use Windows, I do want users who do to be able to run my software.
Same.
...
> WSL is cool and all, but personally I want to ship native Windows
> stuff that "just works" as much as possible. I'm not sure what the
> graphics story is like on WSL these days, but in the past dealing with
> X11 compatibility and GPUs was not easy, or so I've heard. So for me,
> I'd really like to see the MinGW build work acceptably (threads, JIT,
> etc.) Building with MSVC would be even better but I'll take what I
> can get. :) I just get jealous whenever I look at some new language
> implementation (or just some other Scheme) and see that it can do
> native Windows, Linux, and MacOS builds.
I have seen guile-gi launch a program on MinGW using MinGW's
Gtk libraries. I have no benchmarks.
I did attempt a build with MSVC (which is a nightmare because you have
to run autoconf in MSYS and use a batch script to translate gcc
flags into cl flags). It looked pretty bad: so many compilation errors.
I think you'd have to fix all of gnulib and then pull all of gnulib
into Guile, haha.
-Mike
next prev parent reply other threads:[~2023-06-06 21:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1629803116.370682.1686084646758.ref@mail.yahoo.com>
2023-06-06 20:50 ` Guile 64-bit Windows support, redux Mike Gran
2023-06-06 20:56 ` Jean Abou Samra
2023-06-06 21:10 ` [EXT] " Thompson, David
2023-06-06 21:58 ` Mike Gran [this message]
2023-06-08 19:50 ` Maxime Devos
2023-06-08 20:46 ` Mike Gran
2023-06-09 11:01 ` Maxime Devos
2023-06-22 13:36 ` Mike Gran
2023-10-29 21:34 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2023-11-28 21:04 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2023-11-28 22:04 ` Dr. Arne Babenhauserheide
2024-01-04 10:40 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-02-06 6:44 ` Dr. Arne Babenhauserheide
2024-02-07 14:19 ` Thompson, David
2024-02-07 20:19 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-02-07 20:23 ` Thompson, David
2024-02-07 20:29 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-03-20 20:28 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-03-20 20:40 ` Thompson, David
2024-03-23 15:09 ` Jonas Hahnfeld via Developers list for Guile, the GNU extensibility library
2024-03-29 17:20 ` Thompson, David
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=1223010247.378529.1686088704626@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=dthompson2@worcester.edu \
--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).