qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: 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 12:37:33 +0200	[thread overview]
Message-ID: <5061896D.4020107@redhat.com> (raw)
In-Reply-To: <CAFEAcA-1k9xfG_t64z8ZNufVRBg4yG5K14LP_do=Ou2hY5G+mw@mail.gmail.com>

On 09/25/12 11:31, Peter Maydell wrote:
> On 25 September 2012 09:47, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> Even though pixman is used by core linux packages it is still a young
>> project. On older distros (RHEL-5 for example) it isn't included and
>> must be compiled manually.
> 
> 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?

I rarely found a piece of software which builds as easy as pixman.  No
unusual dependencies.  No tricks stuff in the specfile.  You can grab as
source rpm from rhel6 or fedora, rebuild it for rhel5 and be done with
it.  Backports on other distros should likewise be simple.

> So they're a new library -- how good are they at API/ABI stability?

I didn't notice any issues until now (didn't search though).  No soname
bump yet.  And given Xorg + cairo are using pixman they hardly can get
it wrong unnoticed, things would break left+right all over the place if
they did.

> I also note that http://pixman.org/ says "There is currently no
> documentation besides the source code itself", which makes me
> really really wary of using it.

That made me worry too, but it was surprisingly easy to get along with
just the header file and some sample code.  At the end of the day it is
just standard raster ops and transformations built into a library.

cheers,
  Gerd

  reply	other threads:[~2012-09-25 10:37 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 [this message]
2012-09-25 10:48     ` Peter Maydell
2012-09-25 11:00       ` Gerd Hoffmann
2012-09-25 21:18         ` Anthony Liguori
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=5061896D.4020107@redhat.com \
    --to=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).