Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Kang Kai <kai.kang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH 1/3] qt4-native: enable features to build kdelib4-native
Date: Mon, 16 Apr 2012 10:20:31 +0800	[thread overview]
Message-ID: <1334542833-27552-2-git-send-email-kai.kang@windriver.com> (raw)
In-Reply-To: <1334542833-27552-1-git-send-email-kai.kang@windriver.com>

add a bbappend file to enable qt4-native 4.7.4 to enable openssl and
phonon support. Add flags '-no-pch -no-sm' to make qt4-native itself
compiled successfully.

Signed-off-by: Kang Kai <kai.kang@windriver.com>
---
 recipes-misc-support/qt4-native_4.7.4.bbappend |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
 create mode 100644 recipes-misc-support/qt4-native_4.7.4.bbappend

diff --git a/recipes-misc-support/qt4-native_4.7.4.bbappend b/recipes-misc-support/qt4-native_4.7.4.bbappend
new file mode 100644
index 0000000..a11a23f
--- /dev/null
+++ b/recipes-misc-support/qt4-native_4.7.4.bbappend
@@ -0,0 +1,4 @@
+# Needed by kdelibs4-native
+EXTRA_OECONF += "-no-pch -no-sm -openssl"
+
+TOBUILD += "src/phonon"
-- 
1.7.5.4




  reply	other threads:[~2012-04-16  3:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  2:20 [meta-kde] enable kdelib4-native to build makekdewidgets Kang Kai
2012-04-16  2:20 ` Kang Kai [this message]
2012-04-16 10:50   ` [PATCH 1/3] qt4-native: enable features to build kdelib4-native Samuel Stirtzel
2012-04-19  1:48     ` Kang Kai
2012-04-16  2:20 ` [PATCH 2/3] kdelibs4-native: re-add the original recipe Kang Kai
2012-04-16  2:20 ` [PATCH 3/3] kdelib4-native: build makekdewidgets Kang Kai
2012-04-16 10:49   ` Samuel Stirtzel
2012-04-16  4:43 ` [meta-kde] enable kdelib4-native to " Kang Kai
2012-04-16  6:43   ` Samuel Stirtzel

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=1334542833-27552-2-git-send-email-kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-devel@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