unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Peter Brett <peter@peter-b.co.uk>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Reconsideration of MinGW work
Date: Mon, 22 Mar 2010 21:00:01 +0100	[thread overview]
Message-ID: <m3zl20w2im.fsf@pobox.com> (raw)
In-Reply-To: <we1mr5ncydx1.fsf@ssclt003.ee.surrey.ac.uk> (Peter Brett's message of "Mon, 22 Mar 2010 08:10:50 +0000")

Hi Peter (& Neil & co),

On Mon 22 Mar 2010 09:10, Peter Brett <peter@peter-b.co.uk> writes:

> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> I've been making gradual progress on MinGW cross building, but I've
>> reached a point where I'm no longer sure that this is worthwhile.  This
>> email explains why, and invites comments from anyone interested in this
>> - especially from anyone who is really trying to use Guile on Windows.
>
> We get people coming to the gEDA user mailing list on a regular basis
> saying, "Where can I find a version of gEDA for Windows?" and the
> Windows builds we've put out have been generally well-received.  Since
> Guile is one of our core dependencies, lack of Windows support in Guile
> would mean that we wouldn't be able to provide a Windows build at all
> (we already had massive problems at the start of the Guile 1.8.x series
> with GMP portability, or lack thereof, and this meant that it took
> almost three years after 1.8 became the supported stable release for us
> to be able to stop supporting 1.6).

As Neil mentioned, hopefully we can get there via the gnulib path; it
does seem to be the right thing to do GNU-wise in this case. Guile's
code would stay the same, as much as possible, and Gnulib would have
mingw support in it, so that if you compile Guile on mingw, the Gnulib
compat layer gets compiled in.

Sounds acceptable, no? Granted it might take a little while to get it
right, but hopefully not three years.

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2010-03-22 20:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-21 20:51 Reconsideration of MinGW work Neil Jerram
2010-03-21 21:36 ` Grant Rettke
2010-03-22  1:28 ` Ken Raeburn
2010-03-22 20:10   ` Andy Wingo
2010-03-22 23:38   ` Greg Troxel
2010-03-23  0:04   ` Neil Jerram
2010-03-23  6:59     ` Ken Raeburn
2010-03-23  8:50       ` Andy Wingo
2010-03-28 22:32     ` guile on lemote (was Re: Reconsideration of MinGW work) Ken Raeburn
2010-03-29 21:37       ` guile on lemote Neil Jerram
2010-03-22  8:10 ` Reconsideration of MinGW work Peter Brett
2010-03-22 20:00   ` Andy Wingo [this message]
2010-03-22 20:05     ` Linas Vepstas
2010-03-23  0:20       ` Neil Jerram
2010-03-23  0:13   ` Neil Jerram
2010-03-28 22:26 ` Ludovic Courtès
2010-03-29 20:34   ` Neil Jerram
  -- strict thread matches above, loose matches on Subject: below --
2010-03-21 22:45 carlo.bramix
2010-03-23  0:35 ` Reconsideration " Neil Jerram

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=m3zl20w2im.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=peter@peter-b.co.uk \
    /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).