[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Problems with native Mingw-w64 build

From: Mark Cave-Ayland
Subject: Re: [Qemu-devel] Problems with native Mingw-w64 build
Date: Mon, 27 Mar 2017 06:48:46 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.6.0

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
>> <address@hidden> 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?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]