From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] qt4-x11-free: enable -accessibility and -sm
Date: Thu, 12 Apr 2012 22:00:30 +0800 [thread overview]
Message-ID: <4F86DFFE.3010206@windriver.com> (raw)
In-Reply-To: <ac05d9a1b72099761bbc1a8312cd0d4ad8600b4a.1333085308.git.liezhi.yang@windriver.com>
Is there any suggestions for this one please?
// Robert
On 03/30/2012 01:29 PM, Robert Yang wrote:
> Is it possible to enable the "-sm -accessibility" in oe-core, please?
> There is a meta-kde layer which requires the "-sm -accessibility", but
> they are disabled in meta/recipes-qt/qt4/qt4.inc:
>
> QT_DISTRO_FLAGS ?= "-no-accessibility -no-sm"
>
> I checked the log of the qt4, can't find the related log for
> "-no-accessibility -no-sm".
>
> Another way is use the bbappend, but it would be great if it can be
> enabled in oe-core.
>
> This only enables for qt4-x11, doesn't enable for qt4-embedded, and
> have done testing on: qemux86, qemuarm, qemumips, qemuppc.
>
> Signed-off-by: Robert Yang<liezhi.yang@windriver.com>
> ---
> meta/recipes-qt/qt4/qt4-x11-free.inc | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-qt/qt4/qt4-x11-free.inc b/meta/recipes-qt/qt4/qt4-x11-free.inc
> index 072c522..a59198d 100644
> --- a/meta/recipes-qt/qt4/qt4-x11-free.inc
> +++ b/meta/recipes-qt/qt4/qt4-x11-free.inc
> @@ -13,6 +13,9 @@ QT_GLFLAGS_qemuppc = "-opengl"
> QT_CONFIG_FLAGS += "-no-xinerama -no-xkb"
> QT_BASE_LIB ?= "libqt"
>
> +# required by kdelibs4
> +QT_DISTRO_FLAGS = "-accessibility -sm"
> +
> inherit qt4x11
>
> do_install_append() {
next prev parent reply other threads:[~2012-04-12 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 5:29 [PATCH 0/1] qt4-x11-free: enable -accessibility and -sm Robert Yang
2012-03-30 5:29 ` [PATCH 1/1] " Robert Yang
2012-04-12 14:00 ` Robert Yang [this message]
2012-04-13 11:07 ` Richard Purdie
2012-04-27 21:20 ` [PATCH 0/1] " 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=4F86DFFE.3010206@windriver.com \
--to=liezhi.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox