From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: 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: Mon, 27 Mar 2017 06:48:46 +0100 [thread overview]
Message-ID: <9e2591a0-4c25-5f00-0fd3-9c175bfbab12@ilande.co.uk> (raw)
In-Reply-To: <d8a1ecfb-cce1-e855-9f0b-49dccd830155@weilnetz.de>
On 26/03/17 20:54, Stefan Weil wrote:
> Am 26.03.2017 um 14:57 schrieb Peter Maydell:
>> On 26 March 2017 at 11:30, Mark Cave-Ayland
>> <mark.cave-ayland@ilande.co.uk> wrote:
>>> In order to do some testing on a Windows box, I've spent a bit of time
>>> this weekend setting up a mingw-w64 build environment on Windows 10
>>> using http://wiki.qemu-project.org/Hosts/W32 as a guideline.
>>
>> I think most people prefer to use the cross-compile.
>> Stefan might do native compiles.
>
> All installers on https://qemu.weilnetz.de/ are cross built
> on Debian GNU Linux, but from time to time I also build on
> Windows.
>
> Setting up a build environment based on Cygwin works pretty
> well because Cygwin includes most needed packages to cross
> compile for Mingw-w64, both for 32 bit (mingw64-i686-*)
> and 64 bit (mingw64-x86_64-*), see
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=mingw64-&arch=x86_64.
>
> I also use the Cygwin packages on Debian GNU Linux,
> because Debian includes cross tools (compiler, linker)
> for Mingw-w64, but nearly no libraries.
Right, I see cygwin has a much newer version of glib available which
explains how the builds are produced.
What was the exact issue with global symbols which prevents the
pre-built Win64 binaries from glib > 2.22 being used? Or is that
information now obsolete?
ATB,
Mark.
next prev parent reply other threads:[~2017-03-27 5:49 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 [this message]
2017-03-27 20:19 ` Stefan Weil
2017-03-28 7:25 ` Mark Cave-Ayland
2017-03-28 15:16 ` Thomas Huth
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=9e2591a0-4c25-5f00-0fd3-9c175bfbab12@ilande.co.uk \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.