From: <joaquinduran@adtelecom.es>
To: openembedded-devel@openembedded.org
Subject: Using XCB library with cairo
Date: Wed, 17 Oct 2007 01:11:38 +0200 [thread overview]
Message-ID: <MADEUP.15FE19C197103CEF.14572@groups.io> (raw)
Dear all,
Some time ago, Angstrom distribution had configured as virtual/xlib to XCB for some time. Then
xlib was used again due to instability problems (as I remember) with XCB (I've all emails in
computer of work but and I writting from home and I don't have access to them).
I think that one focus of instability could be the integration of cairo with XCB. Today I've
discovered that one of the backends for cairo is XCB, but no cairo package builds it. I would
like to test it, but one of the troubles is how the configuration options could be determined
based on virtual/xlib pacakge. Currently I'm thinking in a similar solution to cairo-fpu:
if virtual/xlib = "xcb" then
EXTRA_OECONF += "--disable-xlib --enable-xcb"
else
EXTRA_OECONF += "--enable-xlib --disable-xcb"
fi
is this possible? any suggestions?
Thanks and Best Regards,
Joaquim Duran
reply other threads:[~2007-10-16 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MADEUP.15FE19C197103CEF.14572@groups.io \
--to=joaquinduran@adtelecom.es \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox