From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Users <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Upcoming 1.6.5 release
Date: Wed, 11 Aug 2004 08:31:23 +0100 [thread overview]
Message-ID: <4119CB4B.1030204@ossau.uklinux.net> (raw)
It might be worth trying to integrate the minor code changes and
instructions that I've worked out for building using MS Visual C on Windows.
However,
- as I understand it, this would need a DOS build script that is
independent of the existing configure stuff
- I'm worried that I may be misunderstanding the benefit of building
using MS Visual C, and should be focussing on building with MINGW instead.
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.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-08-11 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 7:31 Neil Jerram [this message]
2004-08-19 14:58 ` Upcoming 1.6.5 release Rob Browning
-- 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=4119CB4B.1030204@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).