Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] qt4-tools-nativesdk fixes
Date: Sat, 18 Jun 2011 19:56:48 +0100	[thread overview]
Message-ID: <cover.1308423290.git.paul.eggleton@linux.intel.com> (raw)

Several fixes for qt4-tools-nativesdk.

The following changes since commit 835d817f1ba7b99167743fdb86ba80f3a07bd82d:

  systemtap: remove non-core COMPATIBLE_MACHINES (2011-06-16 22:12:40 +0100)

are available in the git repository at:
  git://git.openembedded.org/openembedded-core-contrib paule/qt4-nativesdk-fix
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qt4-nativesdk-fix

Paul Eggleton (3):
  qt4-tools-nativesdk: fix unpack failure due to missing g++.conf
  qt4-tools-nativesdk: drop freetype include as we build with
    -no-freetype
  qt4-tools-nativesdk: fix compile failure in src/dbus

 meta/recipes-qt/qt4/files/qt-dbus-const.patch |   21 +++++++++++++++++++++
 meta/recipes-qt/qt4/qt4-tools-nativesdk.inc   |    7 ++++---
 2 files changed, 25 insertions(+), 3 deletions(-)
 create mode 100644 meta/recipes-qt/qt4/files/qt-dbus-const.patch

-- 
1.7.4.1




             reply	other threads:[~2011-06-18 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 18:56 Paul Eggleton [this message]
2011-06-18 18:56 ` [PATCH 1/3] qt4-tools-nativesdk: fix unpack failure due to missing g++.conf Paul Eggleton
2011-06-20 23:56   ` Khem Raj
2011-06-21  7:37     ` Paul Eggleton
2011-06-18 18:56 ` [PATCH 2/3] qt4-tools-nativesdk: drop freetype include as we build with -no-freetype Paul Eggleton
2011-06-18 18:56 ` [PATCH 3/3] qt4-tools-nativesdk: fix compile failure in src/dbus Paul Eggleton
2011-06-22 16:42 ` [PATCH 0/3] qt4-tools-nativesdk 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.1308423290.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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