From: "Andreas Färber" <andreas.faerber@web.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Scott Wood <scottwood@freescale.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 12 Dec 2012 18:09:37 +0100 [thread overview]
Message-ID: <50C8BA51.1070502@web.de> (raw)
In-Reply-To: <CAFEAcA8RKMinAQZvBGACjaNoTY5Rt8xDW4DX3myAQtX6R1bwiQ@mail.gmail.com>
Am 12.12.2012 17:47, schrieb Peter Maydell:
> On 12 December 2012 03:18, Scott Wood <scottwood@freescale.com> wrote:
>> QEMU is sometimes used in embedded contexts, where graphical support
>> is unnecessary. The ability to turn off graphics support not only
>> saves some space, but it eliminates the dependency on pixman.
>
> I would expect that we'd want to use pixman in the emulation
> of graphics devices (which should be visible to the guest even
> if the host doesn't have display support).
>
>> My immediate motivation was that the QEMU-supplied pixman was being a
>> pain to cross compile
>
> Problems with cross compilation should be reported as bugs
> so we can fix them -- we need to fix them anyway for the more
> common case where there is host graphics support.
I already reported that the submodule does not configure on OSX/ppc
v10.5.8 - apparently due to some PKG_ macros not getting resolved. I
suspected aclocal not picking up pkg.m4 file but setting ACLOCAL_FLAGS
did not help. Do we need a more modern pkg-config version than we are
testing for?
Another issue seemed to be that our Makefile did not take into account
that I may be building with, e.g., "gcc -arch ppc64" and passing a
specific $PATH for 64-bit libraries / aclocal / pkgconfig to our configure.
The latest stable pixman configured but didn't compile on OSX/ppc due to
undefined identifiers or something. (The broken submodule version makes
it unhandy to fix this.)
This is holding up my Cocoa review of the gfx_ hook (that you haven't
jumped in to help out for v1.3) and I seriously doubt that it makes any
difference if I go through the hoops of posting the same info on
Launchpad when it Simply Works(tm) on Linux distros...
Testing on OSX/i386 v10.6 is still on my TODO list.
Andreas
next prev parent reply other threads:[~2012-12-12 17:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 3:18 [Qemu-devel] [RFC PATCH] Allow building without graphics support Scott Wood
2012-12-12 6:46 ` Stefan Weil
2012-12-13 0:48 ` Scott Wood
2012-12-13 6:31 ` Stefan Weil
2012-12-13 15:53 ` Scott Wood
2012-12-13 18:58 ` Stefan Weil
2012-12-13 19:16 ` Scott Wood
2012-12-13 19:32 ` Scott Wood
2012-12-14 8:13 ` Gerd Hoffmann
2012-12-14 18:51 ` Scott Wood
2012-12-19 9:02 ` Gerd Hoffmann
2012-12-19 18:47 ` Scott Wood
2012-12-14 8:07 ` Gerd Hoffmann
2012-12-14 18:48 ` Scott Wood
2012-12-19 9:13 ` Gerd Hoffmann
2012-12-19 18:57 ` Scott Wood
2012-12-20 6:59 ` Gerd Hoffmann
2012-12-20 16:19 ` Scott Wood
2012-12-21 8:56 ` Gerd Hoffmann
2012-12-21 10:56 ` Robert Schiele
2012-12-21 19:01 ` Scott Wood
2012-12-12 7:52 ` Gerd Hoffmann
2012-12-13 0:57 ` Scott Wood
2012-12-13 7:16 ` Gerd Hoffmann
2012-12-13 14:44 ` Alexander Graf
2012-12-13 15:10 ` Peter Maydell
2012-12-13 15:16 ` Gerd Hoffmann
2012-12-13 15:30 ` Alexander Graf
2012-12-13 15:57 ` Scott Wood
2012-12-12 16:28 ` John Spencer
2012-12-12 16:54 ` Andreas Färber
2012-12-13 0:53 ` Scott Wood
2012-12-12 16:47 ` Peter Maydell
2012-12-12 17:09 ` Andreas Färber [this message]
2012-12-12 17:37 ` Peter Maydell
2012-12-12 17:42 ` Paolo Bonzini
2012-12-13 0:51 ` Scott Wood
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=50C8BA51.1070502@web.de \
--to=andreas.faerber@web.de \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=scottwood@freescale.com \
/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).