qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [RfC] using pixman in qemu for raster ops
Date: Tue, 25 Sep 2012 16:18:44 -0500	[thread overview]
Message-ID: <878vbxol6z.fsf@codemonkey.ws> (raw)
In-Reply-To: <50618EBF.2050207@redhat.com>

Gerd Hoffmann <kraxel@redhat.com> writes:

> On 09/25/12 12:48, Peter Maydell wrote:
>> On 25 September 2012 11:37, Gerd Hoffmann <kraxel@redhat.com> wrote:
>>> On 09/25/12 11:31, Peter Maydell wrote:
>>>> For me "not a standard library package on RHEL5" is a strong argument
>>>> against adding a hard dependency. (For instance, most of the compute
>>>> cluster machines here are RHEL5 and it would be pretty awkward to
>>>> deal with manually building a dependent library.)
>>>
>>> Why it is that a big deal?  Whatever is used to distribute qemu to the
>>> cluster machines (local yum repo?) can be used to distribute pixman too, no?
>> 
>> There's a big leap between "run configure, put the qemu executable
>> in some generally available directory" and "you have to first get
>> and build some third party library, install it somewhere, tell
>> configure where you put it, then build qemu, then make sure that
>> not just the qemu executable but also this third party library
>> are on all the machines". At the moment you can build qemu without
>> any non-system dependencies, and we should have a really good
>> reason for breaking that.
>
> Hmm, we could import a pixman copy into the qemu tree and use that as
> fallback if we don't find pixman installed on the system ...

We can include a pixman submodule in qemu.git and have configure try to
find a local version, if it's not available, build the embedded version.

After RHEL5 becomes ancient, we can simply remove the submodule.  Should
make everyone happy.

Regards,

Anthony Liguori

>
> cheers,
>   Gerd

  reply	other threads:[~2012-09-25 21:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-25  8:47 [Qemu-devel] [RfC] using pixman in qemu for raster ops Gerd Hoffmann
2012-09-25  9:31 ` Peter Maydell
2012-09-25 10:37   ` Gerd Hoffmann
2012-09-25 10:48     ` Peter Maydell
2012-09-25 11:00       ` Gerd Hoffmann
2012-09-25 21:18         ` Anthony Liguori [this message]
2012-09-25 14:32       ` Paolo Bonzini
2012-09-25 14:57         ` Peter Maydell
2012-09-25 14:57   ` Paolo Bonzini
2012-09-25 15:31   ` Søren Sandmann
2012-09-25 15:43     ` Gerd Hoffmann
2012-09-25 16:02       ` Søren Sandmann
2012-09-25 16:20         ` Markus Armbruster
2012-09-25 17:08           ` Søren Sandmann
2012-09-26  5:58           ` Gerd Hoffmann
2012-09-25 10:32 ` Stefano Stabellini

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=878vbxol6z.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.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).