From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: libguile on Windows
Date: Tue, 11 Oct 2005 23:37:23 +0100 [thread overview]
Message-ID: <87y84zptng.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <00e301c5cdf5$02aa3d40$6b01a8c0@DORIAN> (Dylan Nicholson's message of "Tue, 11 Oct 2005 09:47:44 +1000")
"Dylan Nicholson" <dylannic@bigpond.net.au> writes:
> Would there be place or purpose to make publically available a version
> of libguile intended for compiling under MSVC?
As far as the core Guile distribution is concerned, I think it depends
on whether there is any practical difference between an MSVC-compiled
libguile DLL and one produced by the MinGW cross-compiler. (This is
something I don't understand yet.)
If there isn't, the fact that (AFAIU) the MinGW approach already works
would make it difficult to justify maintaining an MSVC build approach
in the core distribution.
(Of course someone could maintain an MSVC build independently.)
> The only part I'd really like to fix is the snarfing part - it can *in
> principle* be done automatically, although I'm not exactly sure if the
> dependencies would function 100% reliably.
> Even if it's just a static snapshot of 1.6.5 until someone else can be
> bothered to come along and maintain it, there would surely at least be
> one or two other weirdos like me out there that prefer to work with MS
> products than GNU tools...
Even if you are going to compile using MSVC, the most practical way
(that I'm aware of) to do the snarfing is to do a partial build under
Cygwin first. So GNU tools will always be involved, I think.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-10-11 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 23:23 libguile on Windows Dylan Nicholson
2005-10-10 23:40 ` Neil Jerram
[not found] ` <00e301c5cdf5$02aa3d40$6b01a8c0@DORIAN>
2005-10-11 22:37 ` Neil Jerram [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-10 23:43 Dylan Nicholson
2005-10-10 22:52 Dylan Nicholson
2005-10-10 23:09 ` Neil Jerram
2005-10-10 22:38 Dylan Nicholson
[not found] <001f01c5ca06$9a957db0$6401a8c0@DORIAN>
[not found] ` <87vf07afac.fsf@ossau.uklinux.net>
2005-10-09 21:53 ` Dylan Nicholson
2005-10-10 16:47 ` Neil Jerram
2005-10-10 22:19 ` Dylan Nicholson
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=87y84zptng.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).