From: Rob Browning <rlb@defaultvalue.org>
Cc: Guile Users <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Upcoming 1.6.5 release
Date: Thu, 19 Aug 2004 09:58:08 -0500 [thread overview]
Message-ID: <874qmz41kv.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <4119CB4B.1030204@ossau.uklinux.net> (Neil Jerram's message of "Wed, 11 Aug 2004 08:31:23 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> On the second point, can anyone comment whether there is any practical
> difference between a Guile DLL built with MSVC and one built with
> MINGW? The two points that seem useful to me from MSVC-building are
> (i) direct use of the MS C runtime; (ii) MSVC debugging information.
> But it may be that MINGW could give me these as well.
I'd say fixes for the above would be fine once you can figure out what
the "right thing" is. i.e. whether mingw would be equivalent or not,
etc.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-19 14:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 7:31 Upcoming 1.6.5 release Neil Jerram
2004-08-19 14:58 ` Rob Browning [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-07 17:24 Rob Browning
2004-08-07 19:56 ` Matthias Koeppe
2004-08-08 18:39 ` Rob Browning
2004-08-09 8:38 ` Michael Tuexen
2004-08-09 15:17 ` Andreas Vögele
2004-08-09 16:04 ` Michael Tuexen
2004-08-09 17:17 ` Andreas Vögele
2004-08-09 19:16 ` Michael Tuexen
2004-08-09 19:16 ` Michael Tuexen
2004-08-10 0:20 ` Kevin Ryde
2004-08-10 0:26 ` Kevin Ryde
2004-08-10 9:19 ` Marius Vollmer
2004-08-12 8:10 ` Andreas Vögele
2003-09-20 2:58 Rob Browning
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=874qmz41kv.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--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).