unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-user@gnu.org
Subject: Re: [EXT] relocatable guile on windows
Date: Wed, 7 Dec 2022 08:55:10 -0500	[thread overview]
Message-ID: <CAJ=RwfbxAN5skrcYWonc-GphYtd6A5_VnYVp6ebBCSrHNX6ztA@mail.gmail.com> (raw)
In-Reply-To: <Y4wKd+C/l5TL0biF@spikycactus.com>

Hi Mike,

On Sat, Dec 3, 2022 at 9:49 PM Mike Gran <spk121@yahoo.com> wrote:
>
> Hello Guile,
>
> The Lisp Game Jam was a few weeks ago, and in prep, I took a stab an
> making Guile work better on Windows, using MinGW MSys64 UCRT64 for
> compilation. Little did I imagine that it would take a couple months
> to make something servicable, so I never got around to actually making
> a game.
>
> This Guile is a fork with a lot of hacks for Windows: lack of
> POSIX shell, DLL nonsense, Windows filesystem instead of FHS,
> yadda yadda yadda.  The biggest hack is that of making
> all the file paths relative to the guile executable, so that
> it can be distributed as a single zip file or MSIX install file.

I haven't had a chance to try this out yet but I wanted to say that
this is great work!  I'd really like to have a good story to tell for
shipping games built with Guile and Chickadee on Windows.  In the past
I've tried to cross-compile Guile for Windows from Linux and made it
as far as getting Guile 3 to boot, but the JIT didn't work and I think
threads, though enabled, were broken.  I haven't used Windows for
development in over 10 years so I'm somewhat helpless when things go
wrong.

It would be really great if we could organize a bit around upstreaming
patches for proper Windows support and come up with some documentation
with official recommendations for how to build for Windows.  I never
know what the best approach is: cygwin? mingw? native build (more work
than the other two)?  A lot of other Scheme implementations run on
Windows, so Guile should, too.

- Dave



  parent reply	other threads:[~2022-12-07 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Y4wKd+C/l5TL0biF.ref@spikycactus.com>
2022-12-04  2:48 ` relocatable guile on windows Mike Gran
2022-12-04 10:29   ` Dr. Arne Babenhauserheide
2022-12-04 11:24     ` Dr. Arne Babenhauserheide
2022-12-04 11:10   ` Vivien Kraus
2022-12-07 13:55   ` Thompson, David [this message]
2022-12-08 16:41     ` [EXT] " Mike Gran
2022-12-08  5:56   ` Janneke Nieuwenhuizen
2022-12-08 15:58     ` 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='CAJ=RwfbxAN5skrcYWonc-GphYtd6A5_VnYVp6ebBCSrHNX6ztA@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.com \
    /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).