From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3]: Fix the error when building image "core-image-gtk-directfb"
Date: Fri, 13 Jan 2012 15:06:27 +0800 [thread overview]
Message-ID: <cover.1326437644.git.xiaofeng.yan@windriver.com> (raw)
From: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Hi Saul,
I remove ${sysconfdir}/* because bitbake will package this directory as default.
The following part was previous description.
----------------------------------------------
Bitbake complain " No package 'cairo-xlib' found" when building image "core-image-gtk-directfb".
Misconfiguration of directfb in PACKAGECONFIG causes this problem. I change directfb to gtk-directfb.
Another problem is about messy code when running gtk-demo because of no "/etc/pango".
I create this directory in pango.inc.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: xiaofeng/gtk-directfb
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/gtk-directfb
Thanks,
Xiaofeng Yan <xiaofeng.yan@windriver.com>
---
Xiaofeng Yan (3):
gtk.inc: Change configuration of directfb to gtk-directfb
cairo.inc: Change configuration of directfb to gtk-directfb
pango.inc: add directory "/etc/pango"
meta/recipes-gnome/gtk+/gtk+.inc | 2 +-
meta/recipes-graphics/cairo/cairo.inc | 2 +-
meta/recipes-graphics/pango/pango.inc | 7 ++++++-
3 files changed, 8 insertions(+), 3 deletions(-)
--
1.7.7
next reply other threads:[~2012-01-13 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 7:06 Xiaofeng Yan [this message]
2012-01-13 7:06 ` [PATCH 1/3] gtk.inc: Change configuration of directfb to gtk-directfb Xiaofeng Yan
2012-01-13 7:06 ` [PATCH 2/3] cairo.inc: " Xiaofeng Yan
2012-01-13 7:06 ` [PATCH 3/3] pango.inc: add directory "/etc/pango" Xiaofeng Yan
2012-01-16 4:34 ` Saul Wold
2012-01-17 9:11 ` Khem Raj
2012-01-17 10:13 ` Koen Kooi
2012-01-17 20:37 ` [PATCH 0/3]: Fix the error when building image "core-image-gtk-directfb" Saul Wold
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=cover.1326437644.git.xiaofeng.yan@windriver.com \
--to=xiaofeng.yan@windriver.com \
--cc=openembedded-core@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.