From: Gerd Hoffmann <kraxel@redhat.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Stefan Weil <sw@weilnetz.de>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH] Allow building without graphics support
Date: Wed, 19 Dec 2012 10:02:13 +0100 [thread overview]
Message-ID: <50D18295.8000509@redhat.com> (raw)
In-Reply-To: <1355511117.4740.4@snotra>
On 12/14/12 19:51, Scott Wood wrote:
> On 12/14/2012 02:13:53 AM, Gerd Hoffmann wrote:
>> Hi,
>>
>> > Yes, I could manually install it, though then I get to deal with
>> telling
>> > the pixman build exactly where to install itself, and repeating the
>> > process for each toolchain and multilib-variant thereof.
>>
>> That part is easy too. You just need ${cross_prefix}-pkg-config.
>> A simple two-liner script which sets PKG_CONFIG_PATH, then calls
>> /usr/bin/pkg-config. That will not only work for pixman, but all
>> libraries detected via pkg-config by configure.
>
> I already have that (though I can't just use ${cross_prefx} because I
> have multilib variants to account for, so I set PKG_CONFIG=... when
> running configure), due to the glib dependency.
That works too.
> That just lets pixman
> (and other libraries) be found in the QEMU build; it doesn't reduce the
> burden of building and installing pixman for all targets.
Yep. Pixman isn't different from all other build dependencies though.
Once you have pkg-config working for your cross-build setup it should do
fine for all packages qemu depends on.
cheers,
Gerd
next prev parent reply other threads:[~2012-12-19 9:02 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 [this message]
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
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=50D18295.8000509@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=scottwood@freescale.com \
--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 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).