From: Apelete Seketeli <apelete@seketeli.net>
To: openembedded-devel@openembedded.org
Cc: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Subject: [oe-classic][gtk+][PATCH v2 0/2] gtk+: fix build issue by not building demo programs
Date: Tue, 19 Jun 2012 23:49:33 +0200 [thread overview]
Message-ID: <20120619214933.GG4845@hermes> (raw)
In-Reply-To: <20120619195610.GC4845@hermes>
Hello,
Here is another attempt to fix the following build issue:
| Making all in demos
| make[2]: Entering directory `/home/apelete/devel/bitbake/build/tmp/work/mipsel-oe-linux/gtk+-2.20.1-r10.4/gtk+-2.20.1/demos'
| /usr/bin/gdk-pixbuf-csource --raw --build-list \
| apple_red ./apple-red.png \
| gnome_foot ./gnome-foot.png \
| > test-inline-pixbufs.h \
| || (rm -f test-inline-pixbufs.h && false)
| failed to load "./apple-red.png": Couldn't recognize the image file format for file './apple-red.png'
| make[2]: *** [test-inline-pixbufs.h] Error 1
| make[2]: Leaving directory `/home/apelete/devel/bitbake/build/tmp/work/mipsel-oe-linux/gtk+-2.20.1-r10.4/gtk+-2.20.1/demos'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/home/apelete/devel/bitbake/build/tmp/work/mipsel-oe-linux/gtk+-2.20.1-r10.4/gtk+-2.20.1'
| make: *** [all] Error 2
As a solution, I chose to discard the build of all the demo programs
by removing the corresponding build instructions in demos/Makefile.am
in the source package.
Do we really need those demo programs when building for an embedded
target ?
I also jumped on the occasion to rebase the no-demos.patch that was
applied to gtk+-native only (patch which intentionally disable the
demo prgrams for gtk+-native, but not for target).
The two patches that come as a follow-up of this message are what it's
all about.
Apelete Seketeli (2):
gtk+: Rebase gtk+-2.20.1/no-demos.patch
gtk+: Add no-test-inline-pixbufs.patch to gtk+-2.20.1
recipes/gtk+/gtk+-2.20.1/no-demos.patch | 7 ++++---
.../gtk+/gtk+-2.20.1/no-test-inline-pixbufs.patch | 22 ++++++++++++++++++++
recipes/gtk+/gtk+_2.20.1.bb | 1 +
3 files changed, 27 insertions(+), 3 deletions(-)
create mode 100644 recipes/gtk+/gtk+-2.20.1/no-test-inline-pixbufs.patch
--
1.7.10
--
Apelete
next prev parent reply other threads:[~2012-06-19 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 23:42 [PATCH 0/1] gtk+: Regenerate no-demos.patch and update recipe Apelete Seketeli
2012-06-18 23:42 ` [PATCH 1/1] " Apelete Seketeli
2012-06-19 5:29 ` Martin Jansa
2012-06-19 6:07 ` Apelete Seketeli
2012-06-19 6:34 ` Martin Jansa
2012-06-19 19:56 ` Apelete Seketeli
2012-06-19 21:49 ` Apelete Seketeli [this message]
2012-06-19 21:52 ` [oe-classic][gtk+][PATCH v2 1/2] gtk+: Rebase gtk+-2.20.1/no-demos.patch Apelete Seketeli
2012-06-19 21:55 ` [oe-classic][gtk+][PATCH v2 2/2] gtk+: Add no-test-inline-pixbufs.patch to gtk+-2.20.1 Apelete Seketeli
2012-06-27 16:30 ` Apelete Seketeli
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=20120619214933.GG4845@hermes \
--to=apelete@seketeli.net \
--cc=kristoffer.ericson@gmail.com \
--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 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.