From: Stefan Weil <sw@weilnetz.de>
To: Meador Inge <meadori@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1] ./configure: use -lole32 when building with mingw32
Date: Wed, 15 Feb 2012 20:40:16 +0100 [thread overview]
Message-ID: <4F3C0A20.5070007@weilnetz.de> (raw)
In-Reply-To: <1329324093-6581-1-git-send-email-meadori@codesourcery.com>
Am 15.02.2012 17:41, schrieb Meador Inge:
> glib calls 'CoTaskMemFree' which is defined by ole32.dll.
> Therefore when building with mingw32 -lole32 should be in
> 'LIBS'.
>
> Signed-off-by: Meador Inge <meadori@codesourcery.com>
> ---
> configure | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/configure b/configure
> index 88521d2..40caf81 100755
> --- a/configure
> +++ b/configure
> @@ -502,7 +502,7 @@ if test "$mingw32" = "yes" ; then
> QEMU_CFLAGS="-DWIN32_LEAN_AND_MEAN -DWINVER=0x501 $QEMU_CFLAGS"
> # enable C99/POSIX format strings (needs mingw32-runtime 3.15 or later)
> QEMU_CFLAGS="-D__USE_MINGW_ANSI_STDIO=1 $QEMU_CFLAGS"
> - LIBS="-lwinmm -lws2_32 -liberty -liphlpapi $LIBS"
> + LIBS="-lole32 -lwinmm -lws2_32 -liberty -liphlpapi $LIBS"
> prefix="c:/Program Files/Qemu"
> mandir="\${prefix}"
> datadir="\${prefix}"
Hi,
this would be a workaround for a bug in glib-2.0.
If it requires ole32.dll, it should add it to glib-2.0.pc,
so pkg-config will add it to QEMU.
I never had problems caused by a missing ole32.dll.
Which MinGW do you use (native, cross, version),
and where did you get your glib-2.0 from? My
glib-2.0 has no reference to CoTaskMemFree.
Regards,
Stefan Weil
prev parent reply other threads:[~2012-02-15 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:41 [Qemu-devel] [PATCH v1] ./configure: use -lole32 when building with mingw32 Meador Inge
2012-02-15 16:49 ` Peter Maydell
2012-02-15 17:18 ` Paolo Bonzini
2012-02-15 17:19 ` Meador Inge
2012-02-15 19:40 ` Stefan Weil [this message]
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=4F3C0A20.5070007@weilnetz.de \
--to=sw@weilnetz.de \
--cc=meadori@codesourcery.com \
--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 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.