From: Mike Gran <spk121@yahoo.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guile-user@gnu.org
Subject: Re: [EXT] relocatable guile on windows
Date: Thu, 8 Dec 2022 08:41:28 -0800 [thread overview]
Message-ID: <Y5ITuEKPvqsy1G6x@spikycactus.com> (raw)
In-Reply-To: <CAJ=RwfbxAN5skrcYWonc-GphYtd6A5_VnYVp6ebBCSrHNX6ztA@mail.gmail.com>
On Wed, Dec 07, 2022 at 08:55:10AM -0500, Thompson, David wrote:
> Hi Mike,
>
> On Sat, Dec 3, 2022 at 9:49 PM Mike Gran <spk121@yahoo.com> wrote:
> >
> 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.
Cygwin is basically and emulated POSIX layer using a C library
(newlib) that is fairly similar to GNU libc. Guile builds and works
fine with Cygwin already. The disadvange to Cygwin is that graphical
programs in cygwin require an X server, so they are a bit slow to run
and quite difficult to package up without requiring a downstream user
to get all of Cygwin.
MinGW is basically GCC plus a C library that is definitely not POSIX:
UCRT or MSVCRT, the native Windows libraries. The result is a native
Windows app. It comes with just enough of a shell to run autotools.
Native windows using Microsoft's C compiler is always tough because
autotools doesn't support it without extreme gymnastics. It works
better for CMake programs. I haven't attempted it. It has some quirks
like the lack of #include_next that gnulib depends on.
The long integer patch is the most important and most disruptive if we
want 64-bit windows support. We have to start there, and everything
descends from that. I'm not sure how to gather support for that.
Regards,
Mike Gran
next prev parent reply other threads:[~2022-12-08 16:41 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 ` [EXT] " Thompson, David
2022-12-08 16:41 ` Mike Gran [this message]
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=Y5ITuEKPvqsy1G6x@spikycactus.com \
--to=spk121@yahoo.com \
--cc=dthompson2@worcester.edu \
--cc=guile-user@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).