From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Jamie Lokier <jamie@shareable.org>,
David Turner <digit@google.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix cygwin build and simplify feature detection in 'configure' script
Date: Fri, 12 Jun 2009 11:36:44 +0100 [thread overview]
Message-ID: <4A322FBC.1040704@siriusit.co.uk> (raw)
In-Reply-To: <20090612095502.GA22131@redhat.com>
Daniel P. Berrange wrote:
> There is a mingw64 project that is under active development that aims
> to support both Win32 and Win64 APIs. It may well already be good
> enough to test QEMU builds for Win64, though I've not had personal
> experiance of it
FWIW the Mingw64 port is in reasonably good shape (the only reason it's
still marked as beta is because the project feels they don't want to
change this until all of the gcc languages are supported). They have a
good history of working with open source projects to fix any bugs that
arise, and generally are very helpful with bug reports (perhaps more so
than the original MingW project).
http://sourceforge.net/projects/mingw-w64
ATB,
Mark.
--
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063
next prev parent reply other threads:[~2009-06-12 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 11:53 [Qemu-devel] [PATCH] Fix cygwin build and simplify feature detection in 'configure' script David Turner
2009-06-10 20:52 ` [Qemu-devel] " David Turner
2009-06-10 21:40 ` malc
2009-06-10 22:09 ` David Turner
2009-06-10 22:17 ` Filip Navara
2009-06-10 22:29 ` David Turner
2009-06-10 23:32 ` David Turner
2009-06-11 0:53 ` David Turner
2009-06-10 22:19 ` malc
2009-06-12 2:26 ` Jamie Lokier
2009-06-12 9:55 ` Daniel P. Berrange
2009-06-12 10:36 ` Mark Cave-Ayland [this message]
2009-06-10 21:46 ` Consul
-- strict thread matches above, loose matches on Subject: below --
2009-06-10 22:02 Teemu Nätkinniemi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A322FBC.1040704@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--cc=berrange@redhat.com \
--cc=digit@google.com \
--cc=jamie@shareable.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).