From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: poky@yoctoproject.org
Subject: [PATCH 0/4] Qt4 application fixes
Date: Thu, 23 Dec 2010 15:10:19 +0000 [thread overview]
Message-ID: <cover.1293116495.git.paul.eggleton@linux.intel.com> (raw)
Fix Qt4 runtime dependencies for all of our current Qt4 applications.
Addresses [BUGID: 524].
Some notes:
* qmmp is now building with cmake. This took quite a few additions to
EXTRA_OECMAKE and I suspect there is a case for having a "qt4cmake" bbclass
or similar to make this reusable - further discussion needed.
* qmmp packaging is not perfect, there are still quite a few unpackaged
files; however it should at least now be usable. How much further to go
really depends on the purpose of having it in poky.
Pull URL: git://git.pokylinux.org/poky-contrib.git
Branch: paule/qt-fixes
Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=paule/qt-fixes
Thanks,
Paul Eggleton <paul.eggleton@linux.intel.com>
---
Paul Eggleton (4):
qmake2.bbclass: add space to end of DEPENDS_prepend
fotowall: fix runtime Qt4 dependencies
quicky: fix Qt4 runtime dependencies
qmmp: fix dependencies and packaging
meta/classes/qmake2.bbclass | 2 +-
meta/recipes-qt/qt-apps/fotowall_0.9.bb | 4 ++-
meta/recipes-qt/qt-apps/qmmp_0.4.1.bb | 54 +++++++++++++++++-------------
meta/recipes-qt/qt-apps/quicky_0.4.bb | 1 -
4 files changed, 35 insertions(+), 26 deletions(-)
next reply other threads:[~2010-12-23 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 15:10 Paul Eggleton [this message]
2010-12-23 15:10 ` [PATCH 1/4] qmake2.bbclass: add space to end of DEPENDS_prepend Paul Eggleton
2010-12-23 15:10 ` [PATCH 2/4] fotowall: fix runtime Qt4 dependencies Paul Eggleton
2010-12-23 15:10 ` [PATCH 3/4] quicky: fix Qt4 runtime dependencies Paul Eggleton
2010-12-23 15:10 ` [PATCH 4/4] qmmp: fix dependencies and packaging Paul Eggleton
2010-12-23 16:15 ` [PATCH 0/4] Qt4 application fixes Richard Purdie
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.1293116495.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=poky@yoctoproject.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.