From: Stefan Weil <sw@weilnetz.de>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <Qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] MinGW build
Date: Thu, 27 Nov 2014 22:14:51 +0100 [thread overview]
Message-ID: <5477944B.1000901@weilnetz.de> (raw)
In-Reply-To: <5B49B4C2-D8A6-40A9-A3F8-EFD0865AC3C3@livius.net>
Am 27.11.2014 um 21:52 schrieb Liviu Ionescu:
>
> On 27 Nov 2014, at 22:09, Stefan Weil <sw@weilnetz.de> wrote:
>
>> ... use Mingw-w64. It compiles QEMU ...
>
> one of my requirements for a Windows version of QEMU is to be statically linked, and do not depend on third party libraries that are not present in a common Windows installation.
Do you really need statically linked executables (they might need a lot
of disk space if you install all of them), or is it sufficient to
distribute all third party libraries which are needed to run QEMU
together with the executables (as I do it with my installers for Windows
on http://qemu.weilnetz.de/)? Even with a statically linked executable,
you won't get a one-file-distribution because QEMU needs a lot of
additional files during runtime (keyboard maps, firmware images, ...).
>
> do you have a build procedure with Mingw-w64 that creates a static program? what libraries are needed, where do you get them or how do you build them as static libraries?
Up to now, I never have build a static QEMU executable for Windows, so I
simply don't know which problems might occur and which libraries are
available for static linking or not.
Stefan
next prev parent reply other threads:[~2014-11-27 21:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:55 [Qemu-devel] MinGW build Liviu Ionescu
2014-11-26 20:13 ` Peter Maydell
2014-11-26 20:19 ` Stefan Weil
2014-11-26 21:44 ` Liviu Ionescu
2014-11-27 16:43 ` Liviu Ionescu
2014-11-27 19:34 ` Peter Maydell
2014-11-27 19:57 ` Liviu Ionescu
2014-11-27 20:09 ` Stefan Weil
2014-11-27 20:14 ` Liviu Ionescu
2014-11-27 20:18 ` Peter Maydell
2014-11-27 20:27 ` Liviu Ionescu
2014-11-27 22:04 ` Peter Maydell
2014-11-28 0:30 ` Liviu Ionescu
2014-11-28 7:14 ` Stefan Weil
2014-11-28 8:41 ` Peter Maydell
2015-11-27 18:49 ` Peter Maydell
2015-11-27 19:16 ` Stefan Weil
2015-11-27 21:05 ` Peter Maydell
2015-11-29 12:03 ` Juan Quintela
2015-12-03 11:58 ` Peter Maydell
2015-12-03 14:15 ` Peter Maydell
2015-12-03 14:30 ` Juan Quintela
2015-11-30 13:24 ` Juan Quintela
2015-11-30 13:29 ` Stefan Weil
2014-11-27 20:52 ` Liviu Ionescu
2014-11-27 21:14 ` Stefan Weil [this message]
2014-11-27 21:38 ` Liviu Ionescu
2014-11-28 6:20 ` Stefan Weil
2014-11-28 6:23 ` Liviu Ionescu
2014-11-28 7:03 ` Stefan Weil
2014-12-01 10:30 ` Liviu Ionescu
2014-12-01 18:42 ` Stefan Weil
2014-12-02 18:28 ` Liviu Ionescu
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=5477944B.1000901@weilnetz.de \
--to=sw@weilnetz.de \
--cc=Qemu-devel@nongnu.org \
--cc=ilg@livius.net \
--cc=peter.maydell@linaro.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 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.