From: Thomas Huth <thuth@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
Stefan Weil <sw@weilnetz.de>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Problems with native Mingw-w64 build
Date: Tue, 28 Mar 2017 17:16:36 +0200 [thread overview]
Message-ID: <e776dac5-ea72-efaf-c9d5-6b98f49e47e7@redhat.com> (raw)
In-Reply-To: <360a7047-6190-c006-e155-1166ab14b83a@ilande.co.uk>
On 28.03.2017 09:25, Mark Cave-Ayland wrote:
[...]
> I ended up starting again from scratch last night and trying the build
> with MSYS2 instead. MSYS2 has really improved since I last looked at it
> a couple of years back, and I was able to get a working build
> environment all set and working without any issues, i.e. set up the
> build environment, run configure, make and make install.
>
> I did make a few notes during installation so if people think it's
> useful I can work through them again and come up with something suitable
> for the wiki.
We've already got a page with instructions for building with MingW:
http://wiki.qemu-project.org/Hosts/W32
So that might be a good place to add your experience with MSYS, I guess?
Thomas
next prev parent reply other threads:[~2017-03-28 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 10:30 [Qemu-devel] Problems with native Mingw-w64 build Mark Cave-Ayland
2017-03-26 12:57 ` Peter Maydell
2017-03-26 19:54 ` Stefan Weil
2017-03-27 5:48 ` Mark Cave-Ayland
2017-03-27 20:19 ` Stefan Weil
2017-03-28 7:25 ` Mark Cave-Ayland
2017-03-28 15:16 ` Thomas Huth [this message]
2017-03-31 17:08 ` Mark Cave-Ayland
2017-03-31 18:38 ` Stefan Weil
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=e776dac5-ea72-efaf-c9d5-6b98f49e47e7@redhat.com \
--to=thuth@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).